with scrum programming values
Each morning we check in with our team for a few minutes. We identify issues blocking progress and changes that need to be addressed.
The work throughout the project is separated into sprints. “Sprints” are time boxes of 2-4 weeks during which the team builds useful and potentially releaseable product increments. In this sense, each sprint could be considered a small project on its own, after which progress can be reviewed, issues identified and changes addressed more easily. This means also that we can react to bugs and manage changing requirements of all sizes. This allows for flexibility, iteration and a result oriented development process.
Sprints are set timeframes which allow the team to review their product, adjust to new information and apply learnings. Sprints further require the product owner to regularly review the priorities of the product development team at the beginning of the cycle. This is when progress is reviewed and ToDo’s for the next sprint are set.
Spec documents and tech plans are only helpful throughout this process
as far as they define the initial direction and provide premises from
which one can divert when new information is acquired. As Helmuth von
Moltke noted in the 19th century
The tactical result of an engagement forms the base for new
strategic decisions because victory or defeat in a battle changes
the situation to such a degree that no human acumen is able to see
beyond the first battle.
Reasons to use agile the agile development process:
- Iterative design over big design up front
- Experimentation over elaborate planning
- Customer feedback over intuition
- Collaborative work over one hero
Our team has repeatedly worked with agile software development methods benefiting from their ability to change direction and priorities when needed. If you have questions on how these methods can be translated into the development of your product then schedule a call with us.