Teams and roles
Assemble teams and assign team members their roles in the project. Extend the Scrum roles with the wonderful RACI principle. Track Team Velocity and collaborate across locations. Use the comment function for discussions and the built-in support of hierarchical organizational structures to keep an overview even in large organizations.
Backlog management
Create Backlogs and structure them by Business Value, implementation effort, or any other tags. With Allegra's Scrum Tool, you can organize uncomplicated Epics and User Stories, which you can further break down into tasks and subtasks.
Release management
Plan long term releases with release dates based on expected team speed and burn-up. Combine with the earned value method to see immediately if something goes wrong.
Sprint management
Organize sprints visually and distribute the tasks to your teams. Immediately recognize which teams are overloaded and correct the utilization. Take vacation, weekend work, and individual absences into account.
Task boards
Put together your very own Scrum Task Boards. Assign any sorting criteria to columns and swim lanes. Design the cards with the appropriate attributes. Drag entries from the backlog into a sprint and move tasks through the workflow in a visually-appealing way.
Burn down charts
In Scrum, burn down charts help to show the progress of the project. They display the number of story points or user stories to be implemented and the number of those actually implemented over the period of a sprint, release, or a completed product.
Kanban boards
If you don't need sprints, you can use the Kanban board. With a Kanban board, you can map your workflows perfectly and capture the eye.
Time tracking
In Scrum, burn down charts help to show the progress of the project. They display the number of story points or user stories to be implemented and the number of those actually implemented over the period of a sprint, release, or complete product.
More reasons to love Allegra
Anonymous test drive
Quickly check out Allegra with our demo installation completely anonymously.
Run on your computer
You can install Allegra on your machine and try it for 30 days for free. We are happy to help you getting started.
Request a webinar
Contact us for a free webinar without any obligation.
Thank you!
We will contact you shortly!
What does scrum mean?
Scrum is a form of agile project management - a method that is used in product development projects - especially software products. Scrum was developed because the methods of classic project management do not always show the desired success with excessive deadlines and budgets as well as results that do not meet the requirements. The term comes from the sport of rugby. Here "Scrum" means a dense bunch of players, who are fighting for the game equipment or the rugby ball. "Scrum" means "scrum" in German. This image is transferred to the project management. Scrum is supposed to say what is particularly important in project management: flexibility, dynamism and daily meetings to coordinate tasks.
How exactly does Scrum work?
After Scrum, the project team is divided into small, self-organizing and cross-functional teams. The product is assembled from many small individual parts, with each individual part having its own verifiable value for the overall project. The teams take turns to develop the parts and work through the list until a useful overall product is created. Scrum structures everything to be done on a timeline in short phases or iterations. In Scrum, such an iteration is called a "sprint". A sprint is a time window of one month or less in which a product increment is generated. A product increment is characterized by the fact that it is tested, adequately documented and operational. A new sprint begins immediately after the previous one is completed.
What scrum roles are there?
Product Owner
The product owner is responsible for the profitability of the product he manages over its life cycle. In Scrum, he controls the order in which tasks in the team's task list are processed. He is also responsible for documenting the requirements, often in the form of so-called epics or user stories.
Scrum master
The Scrum Master should lead the team to ever higher levels of cohesion, self-organization and performance. He is a Scrum expert and, as a coach, helps the team learn and apply the Scrum methodology so that the team takes maximum advantage of it. The Scrum Master is the enabler - always available for the team to help them remove obstacles. He is not the boss of the team. This is a position on par with the team, apart from responsibility and knowledge.
Scrum team members
A Scrum team has between five and nine team members. They work closely together and organize all tasks and effort estimates themselves. There is no hierarchy in the team. Everyone has the same rights and obligations. The Scrum team should have all the skills necessary to independently implement user stories and create the desired product. It is important that the team members are there because of their own motivation - so they should be able to choose their projects themselves - this avoids the mindset "is not my job". This in turn presupposes a sense of responsibility on the part of team members and trust in the managers.
