The Scrum Method
By creating a time framework, and breaking a project into increments, or sprints, a development team can better monitor and manage the project. Assemble a team that meets daily to compare goals for the day. Any concerns can be resolved at sprint review meetings and the sprint retrospective.
The goal of the retrospective is to identify what went wrong at the previous sprint, brings focus to any issues for immediate resolution.
The use of a backlog keeps the product concerns in front of the team for consideration.
The product owner manages the backlog
Monitors the development team against the project’s assessment of business needs
As each sprint completes, the customer reviews the progress
Determining backlog items that need immediate addressing, the team can address market change, or security risks that may affect use of the product. At the end of each sprint the product must be usable for customer review to that point.
A task board with swim lines is useful in determining progress.
What needs to be done
What has already been done
What has been tested
Issues identified as project moves forward, and customer needs reevaluated. The scrum method allows for resolutions and improvements during production.
A burn down chart shows daily progress of sprints.
Control of time and money needed for completion of a project.
The result is a better product with built in assurance for the customer.