Prioritization in Agile

Agile projects are selected based on the aspects and considerations. Prioritization and planning is where most of the effort and time is spent in agile project management. In order to make that happen, there are considerable variables that need to coordinate, as well as numerous agile project management frameworks and methodologies to implement. Before we roll up our sleeves and start practicing the concepts and performing the day ­to ­day efforts that make agile project work a reality, we need to do one final task, which is to prioritize our needs —

Stage 1: The product vision is established: This is where you want the project to go. What do you want the project and its products and services to achieve? Just as important is the questions around why we have selected this product. How does this product support the needs of our organization or remove the barriers to success? What is the risk if we don’t develop the product?

Stage 2: The product roadmap is laid out: ​The product roadmap is created by the product owner. The product roadmap lays out the high level path of the product and its required features.

Stage 3: The release plan is created: ​Like the product roadmap, the release plan is developed by the product owner. Based on the roadmap, a high-­level timetable can be laid out. Based on the prioritization of features, functions, and other requirements, the highest priority items for release are placed earlier in the timetable. Lower priority releases are placed later in the timetable.

Stage 4: The iterations (a.k.a. sprints) are planned: ​The iterations are the short term plans on the work that will be accomplished during that specific timebox. The sprints are planned and coordinated by the ScrumMaster, product owner, and the development team. As we progress in the stages, our focus becomes more attuned and shorter termed. How to plan out each iteration is an art and there are many different techniques in doing so.

Stage 5: The daily standup meetings take place and daily plans are made: ​In agile project management a best practice is the use of short daily meetings — typically 10 to 15 minutes — to level out the agile team, align efforts, and coordinate the actions and the priorities of the day ahead.

Stage 6: The sprint reviews show progress.: As we make our way down the road, we should have something to show for it. Every sprint is planned to make progress. The sprint reviews are our time to demonstrate that progress. For example, in a project, we can demonstrate the secure enrollment process used to register a particular company owned device the employee is going to use.

Stage 7: The retrospective looks at how things went and what can be learned: ​Looking back is something that should not be overlooked. Trudging forward with our heads down may seem like a good idea when we feel like we are making progress or are behind schedule and desperately trying to catch, but looking up and looking back are important. There are plenty of lessons that can be learned every sprint or every day. Repeating mistakes by not leveraging new learning would be wasteful.

Leave a Reply

Your email address will not be published. Required fields are marked *