The Agile Playbook
A How-To Guide on Executing Agile Right From the Start
Start
The Agile Playbook
DONE
IDEA
READY
DOING
PRIORITY
Priority
Ready
Done
Doing
INTEGRATION
FEATURE REFINEMENT
SPRINT PLANNING
IDENTIFY USER
Idea
DESCRIBE IDEA
FEATURE PLANNING
DEFINE BENEFIT
DEPLOYMENT
SCRUM
PRETOTYPE
PLAN REVIEW
IDENTIFY OWNER
REFINEMENT
ACCEPT TEST
GOAL SETTING
BRUTAL ESTIMATE
NEW IDEAS
SPRINT REVIEW
DEFINE IF IT IS NEW/CHANGE
PORTFOLIO KANBAN
SPRINT RETROSPECTIVE
IDEA
A new idea is added to the funnel as an epic
DESCRIBE IDEA
IDENTIFY OWNER
DEFINE IF IT IS NEW/CHANGE
DESCRIBE IDEA
WHO: Idea is described by the originator. This could be the Customer, Product Owner or Developer. WHAT: Describe who has the need, what they want to achieve and how they will benefit from it. Make it brief. Preferably in a format that can be on a post-it. Place the idea on the Portfolio Kanban board. WHY: The idea should be written down using SMART (Specific, Measureable, Attainable, Realistic and Time Bound) to enable conversations.
IDEA
IDENTIFY OWNER
WHO: Product Owner WHAT: Identify a customer who needs the outcome of the idea and is able to give feedback iteratively and incremental on development. WHY: Developers and Product Owners must work closely with the customer to be able to deliver valuable solutions.
IDEA
DEFINE IF IT IS NEW/CHANGE
WHO: Developers and Product Owner WHAT: Developers define wheter the idea is a change to existing features or a new feature in itself. WHY: Knowing if the idea is concerning a change to existing features makes it easier for the developers and product owner to determine if it is within the current scope/vision for the product or not.
IDEA
PRIORITY
An epic is prioritized based on cost, business value, opportunities, etc. It starts as a rough idea and will be prioritized on the Portfolio Kanban.
IDENTIFY USER
DEFINE BENEFIT
PRETOTYPE
BRUTAL ESTIMATE
PORTFOLIO KANBAN
IDENTIFY USER
WHO: Product Owner and Developers WHAT: Discuss with the author of the idea on who would be the potential receiver and user of the outcome. WHY: Working on a new idea it is crucial to identify the receiver to collaborate towards a success.
PRIORITY
DEFINE BENEFIT
WHO: Product Owner, Customer, and Developers WHAT: New ideas should always be beneficial for the user, otherwise they should be cancelled. WHY: Collaborate with the user to define the benefit of the idea. The benefit could be described in many ways: economical, increase in user base, etc. It may be a good idea to define the benefit using Business Value Game.
PRIORITY
PRETOTYPE
WHO: Product Owner, Customer and Developers WHAT: Build a cheap sketch, illustration or mockup with out investing in development. The purpose is to validate that the user can benefit from the outcome and to verify that the team is able to build it. Depending on the idea it will be a good idea use some of the following techniques: Pretotyping, Design Sprint, Shaping, Hackathon, Mob-programming, etc. WHY: Illustrate the idea to confirm benefit and feasibility.
PRIORITY
BRUTAL ESTIMATE
WHO: Developers WHAT: Based on the pretotype the idea can be relatively estimated using Story Points, T-Shirt Sizing, etc. WHY: The brutal estimate is used for prioritizing the idea against other great ideas.
PRIORITY
PORTFOLIO KANBAN
WHO: Product Owner and Customers are key persons. Scrum Master facilitates. WHAT: Update the Portfolio Kanban at the recurring Portfolio Scrum event. The Portfolio Kanban is a board showing the state of the Product Backlog. It visualizes the flow of work items processed by the Developers. Product Owner and Customers collaborate on ranking and prioritising the Product Backlog. Impediments raised by the Developers can be discussed to determine if the investment in active work items is still relevant or if something else needs to be prioritised. The portfolio kanban meeting should be as often as needed. Ideally once a week. Here's a typical agenda for the meeting:What has happened since last time?What will happen until next time?Any new or updated impediments, issues or risks? WHY: To visualize flow and discuss priorities, ranking and impediments.
PRIORITY
READY
To be ready, it's crucial to to know what is needed and how to build it. Here, an epic is refined into features, and sketches are co-created with users and planned.
+ info
FEATURE REFINEMENT
FEATURE PLANNING
PLAN REVIEW
GOAL SETTING
FEATURE REFINEMENT
WHO: Product Owner with help from Developers WHAT: Refinement Activities: Prioritised features and epics Expected delivery date from users List of involved users available for collaboration WHY: Build a feasible plan for the super sprint
READY
FEATURE PLANNING
WHO: Developers and Product Owner. Facilitation is done by Scrum Master. WHAT: Team plans how to deliver as many of the prioritized features and epics as possible: Update realistic capacity for each team member in the coming super sprintsCreate/update important datesCreate/update epicsCreate/update featuresCreate/update goal setting with mapping features and important datesCreate/update user stories for the featuresEstimate the user storyScope the user story for sprint completion. Break up larger user stories to fit.Plan the user story in a specific sprintCreate tasks for the first sprintVerify that estimates match capacity in the team for the coming super sprint or make adjustmentsNote dependencies, issues, risks, decisions that may hinder the progress. WHY: To build a feasible plan for a super sprint.
READY
PLAN REVIEW
WHO: Product Owner and Customers WHAT: If necessary the Product Owner calls for a review of the super sprint plan before presenting at Goal Setting to make sure that potential gaps are identified and managed. WHY: Assert that the plan is building what users and stakeholder needs.
READY
GOAL SETTING
"Hello"
WHO: Developers, Product Owner and Scrum Master WHAT: Walk through of super sprint plan to identify issues, dependencies and risks. Build a goal for the super sprint to be used as overall goal for the involved sprints. WHY: Agree on a long-term objective for the Scrum team. They must fulfill the long-term goal through short-term sprint goals.
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore"
READY
DOING
User stories are developed by the team alongside users to enable features.
+ info
SPRINT PLANNING
SCRUM
REFINEMENT
SPRINT REVIEW
SPRINT RETROSPECTIVE
SPRINT PLANNING
WHO: Scrum Master facilitates, Product Owner has refined the Product Backlog with Developers. WHAT: Given an updated capacity the team pulls user stories in the sprint and create a sprint plan and sprint goal:Update team capacity and availabilityMove agreed ”left overs” from previous sprint into currentIdentify dependencies to/from planned user storiesVerify that all tasks are assigned to team membersComittment from team that the plan is doableDetermine impact on Super Sprint Plan for work that is moving between sprintsAgree on Sprint Goal WHY: Build a feasible plan for the sprint
DOING
SCRUM
WHO: Developers, Scrum Master (or Developer) facilitates, Product Owner is allowed to observe and answer questions. WHAT: Daily meeting with focus on collaboration, impediment busting and progress:Tasks are updated before the meeting (status, remaining work reduced/increased, completed work is updated) At the meeting:Discuss if the team is on track for completion, what is hindering completion and who can help WHY: Team collaborates on reaching the Sprint Goal. Any impediments, blocks, etc. are discussed.
"Hello"
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore"
DOING
WHO: Product Owner and Developers, Scrum Master often facilitates. WHAT: Prepare work for next sprint planning:Product Owner created and prioritized user stories for next sprintsTeam identifies competencies neededTeam discusses the tasks and estimatesIdentify dependencies to/from planned user storiesPreparation by Product Owner (feel free to get help from team):User story, Features and Epics createdUser story prioritizedUser story understood (who needs it, what do the expect and why do they need it)Output:Draft plan for next sprint updatedDepedencies or impediments for starting the work are identified and handled WHY: Make sure that user stories are ready for next sprint.
REFINEMENT
DOING
SPRINT REVIEW
"Hello"
WHO: Developers and Customers, Scrum Master or Product Owner facilitates. WHAT: Completed user stories are demonstrated to the stakeholders by the team. WHY: Inspect outcome of sprint and discuss further adaption.
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore"
DOING
SPRINT RETROSPECTIVE
WHO: Developers, Scrum master facilitates WHAT: Improve the teams way of collaborating and delivering:Celebrate what worksIdentify what can improveCreate tasks to become better WHY: Plan ways to continue improving quality and effectiveness.
DOING
DONE
Here, features are delivered to users on demand
+ info
INTEGRATION
DEPLOYMENT
ACCEPT TEST
NEW IDEAS
INTEGRATION
WHO: Developers WHAT: Compile, Validate, Review, Unit Test, System Test and Integration Test. WHY: All developed products should be integrated often to reduce the risk of single pieces not working when assembled in a larger puzzle
DONE
DEPLOYMENT
WHO: Developers WHAT: Deploy to test servers, Deploy to product servers, Configuration management and Containerization. WHY: To deliver the developed products as fast as possible to start harvesting the benefits.
DONE
ACCEPT TEST
WHO: Customers, Developers and Product Owner WHAT: Customer test the product, Developers fixes issues and Product Owner records any new ideas. WHY: To confirm that the developed products fits the purpose of the customer.
DONE
NEW IDEAS
WHO: Customers, Developers and Product Owner WHAT: Throughout the whole process everyone should be creative and enable idea generation. All ideas could turn into new pieces of work. New ideas are added to the Portfolio Kanban Board and ignite the flow starting with the Idea activities. WHY: To capture any relevant ideas to enhance the product.
DONE
GLOSSARY
SCRUM MASTER
SCALING
PORTFOLIO KANBAN BOARD
CUSTOMER
SCRUM
PRODUCT OWNER
AGILE MANIFESTO
DEVELOPERS
AGILE MINDSET
THE AGILE PLAYBOOK
Monique Vieu
Created on December 17, 2021
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Dynamic Visual Presentation
View
Corporate Christmas Presentation
View
Customer Service Manual
View
Business Results Presentation
View
Meeting Plan Presentation
View
Business vision deck
View
Economic Presentation
Explore all templates
Transcript
The Agile Playbook
A How-To Guide on Executing Agile Right From the Start
Start
The Agile Playbook
DONE
IDEA
READY
DOING
PRIORITY
Priority
Ready
Done
Doing
INTEGRATION
FEATURE REFINEMENT
SPRINT PLANNING
IDENTIFY USER
Idea
DESCRIBE IDEA
FEATURE PLANNING
DEFINE BENEFIT
DEPLOYMENT
SCRUM
PRETOTYPE
PLAN REVIEW
IDENTIFY OWNER
REFINEMENT
ACCEPT TEST
GOAL SETTING
BRUTAL ESTIMATE
NEW IDEAS
SPRINT REVIEW
DEFINE IF IT IS NEW/CHANGE
PORTFOLIO KANBAN
SPRINT RETROSPECTIVE
IDEA
A new idea is added to the funnel as an epic
DESCRIBE IDEA
IDENTIFY OWNER
DEFINE IF IT IS NEW/CHANGE
DESCRIBE IDEA
WHO: Idea is described by the originator. This could be the Customer, Product Owner or Developer. WHAT: Describe who has the need, what they want to achieve and how they will benefit from it. Make it brief. Preferably in a format that can be on a post-it. Place the idea on the Portfolio Kanban board. WHY: The idea should be written down using SMART (Specific, Measureable, Attainable, Realistic and Time Bound) to enable conversations.
IDEA
IDENTIFY OWNER
WHO: Product Owner WHAT: Identify a customer who needs the outcome of the idea and is able to give feedback iteratively and incremental on development. WHY: Developers and Product Owners must work closely with the customer to be able to deliver valuable solutions.
IDEA
DEFINE IF IT IS NEW/CHANGE
WHO: Developers and Product Owner WHAT: Developers define wheter the idea is a change to existing features or a new feature in itself. WHY: Knowing if the idea is concerning a change to existing features makes it easier for the developers and product owner to determine if it is within the current scope/vision for the product or not.
IDEA
PRIORITY
An epic is prioritized based on cost, business value, opportunities, etc. It starts as a rough idea and will be prioritized on the Portfolio Kanban.
IDENTIFY USER
DEFINE BENEFIT
PRETOTYPE
BRUTAL ESTIMATE
PORTFOLIO KANBAN
IDENTIFY USER
WHO: Product Owner and Developers WHAT: Discuss with the author of the idea on who would be the potential receiver and user of the outcome. WHY: Working on a new idea it is crucial to identify the receiver to collaborate towards a success.
PRIORITY
DEFINE BENEFIT
WHO: Product Owner, Customer, and Developers WHAT: New ideas should always be beneficial for the user, otherwise they should be cancelled. WHY: Collaborate with the user to define the benefit of the idea. The benefit could be described in many ways: economical, increase in user base, etc. It may be a good idea to define the benefit using Business Value Game.
PRIORITY
PRETOTYPE
WHO: Product Owner, Customer and Developers WHAT: Build a cheap sketch, illustration or mockup with out investing in development. The purpose is to validate that the user can benefit from the outcome and to verify that the team is able to build it. Depending on the idea it will be a good idea use some of the following techniques: Pretotyping, Design Sprint, Shaping, Hackathon, Mob-programming, etc. WHY: Illustrate the idea to confirm benefit and feasibility.
PRIORITY
BRUTAL ESTIMATE
WHO: Developers WHAT: Based on the pretotype the idea can be relatively estimated using Story Points, T-Shirt Sizing, etc. WHY: The brutal estimate is used for prioritizing the idea against other great ideas.
PRIORITY
PORTFOLIO KANBAN
WHO: Product Owner and Customers are key persons. Scrum Master facilitates. WHAT: Update the Portfolio Kanban at the recurring Portfolio Scrum event. The Portfolio Kanban is a board showing the state of the Product Backlog. It visualizes the flow of work items processed by the Developers. Product Owner and Customers collaborate on ranking and prioritising the Product Backlog. Impediments raised by the Developers can be discussed to determine if the investment in active work items is still relevant or if something else needs to be prioritised. The portfolio kanban meeting should be as often as needed. Ideally once a week. Here's a typical agenda for the meeting:What has happened since last time?What will happen until next time?Any new or updated impediments, issues or risks? WHY: To visualize flow and discuss priorities, ranking and impediments.
PRIORITY
READY
To be ready, it's crucial to to know what is needed and how to build it. Here, an epic is refined into features, and sketches are co-created with users and planned.
+ info
FEATURE REFINEMENT
FEATURE PLANNING
PLAN REVIEW
GOAL SETTING
FEATURE REFINEMENT
WHO: Product Owner with help from Developers WHAT: Refinement Activities: Prioritised features and epics Expected delivery date from users List of involved users available for collaboration WHY: Build a feasible plan for the super sprint
READY
FEATURE PLANNING
WHO: Developers and Product Owner. Facilitation is done by Scrum Master. WHAT: Team plans how to deliver as many of the prioritized features and epics as possible: Update realistic capacity for each team member in the coming super sprintsCreate/update important datesCreate/update epicsCreate/update featuresCreate/update goal setting with mapping features and important datesCreate/update user stories for the featuresEstimate the user storyScope the user story for sprint completion. Break up larger user stories to fit.Plan the user story in a specific sprintCreate tasks for the first sprintVerify that estimates match capacity in the team for the coming super sprint or make adjustmentsNote dependencies, issues, risks, decisions that may hinder the progress. WHY: To build a feasible plan for a super sprint.
READY
PLAN REVIEW
WHO: Product Owner and Customers WHAT: If necessary the Product Owner calls for a review of the super sprint plan before presenting at Goal Setting to make sure that potential gaps are identified and managed. WHY: Assert that the plan is building what users and stakeholder needs.
READY
GOAL SETTING
"Hello"
WHO: Developers, Product Owner and Scrum Master WHAT: Walk through of super sprint plan to identify issues, dependencies and risks. Build a goal for the super sprint to be used as overall goal for the involved sprints. WHY: Agree on a long-term objective for the Scrum team. They must fulfill the long-term goal through short-term sprint goals.
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore"
READY
DOING
User stories are developed by the team alongside users to enable features.
+ info
SPRINT PLANNING
SCRUM
REFINEMENT
SPRINT REVIEW
SPRINT RETROSPECTIVE
SPRINT PLANNING
WHO: Scrum Master facilitates, Product Owner has refined the Product Backlog with Developers. WHAT: Given an updated capacity the team pulls user stories in the sprint and create a sprint plan and sprint goal:Update team capacity and availabilityMove agreed ”left overs” from previous sprint into currentIdentify dependencies to/from planned user storiesVerify that all tasks are assigned to team membersComittment from team that the plan is doableDetermine impact on Super Sprint Plan for work that is moving between sprintsAgree on Sprint Goal WHY: Build a feasible plan for the sprint
DOING
SCRUM
WHO: Developers, Scrum Master (or Developer) facilitates, Product Owner is allowed to observe and answer questions. WHAT: Daily meeting with focus on collaboration, impediment busting and progress:Tasks are updated before the meeting (status, remaining work reduced/increased, completed work is updated) At the meeting:Discuss if the team is on track for completion, what is hindering completion and who can help WHY: Team collaborates on reaching the Sprint Goal. Any impediments, blocks, etc. are discussed.
"Hello"
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore"
DOING
WHO: Product Owner and Developers, Scrum Master often facilitates. WHAT: Prepare work for next sprint planning:Product Owner created and prioritized user stories for next sprintsTeam identifies competencies neededTeam discusses the tasks and estimatesIdentify dependencies to/from planned user storiesPreparation by Product Owner (feel free to get help from team):User story, Features and Epics createdUser story prioritizedUser story understood (who needs it, what do the expect and why do they need it)Output:Draft plan for next sprint updatedDepedencies or impediments for starting the work are identified and handled WHY: Make sure that user stories are ready for next sprint.
REFINEMENT
DOING
SPRINT REVIEW
"Hello"
WHO: Developers and Customers, Scrum Master or Product Owner facilitates. WHAT: Completed user stories are demonstrated to the stakeholders by the team. WHY: Inspect outcome of sprint and discuss further adaption.
"Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore"
DOING
SPRINT RETROSPECTIVE
WHO: Developers, Scrum master facilitates WHAT: Improve the teams way of collaborating and delivering:Celebrate what worksIdentify what can improveCreate tasks to become better WHY: Plan ways to continue improving quality and effectiveness.
DOING
DONE
Here, features are delivered to users on demand
+ info
INTEGRATION
DEPLOYMENT
ACCEPT TEST
NEW IDEAS
INTEGRATION
WHO: Developers WHAT: Compile, Validate, Review, Unit Test, System Test and Integration Test. WHY: All developed products should be integrated often to reduce the risk of single pieces not working when assembled in a larger puzzle
DONE
DEPLOYMENT
WHO: Developers WHAT: Deploy to test servers, Deploy to product servers, Configuration management and Containerization. WHY: To deliver the developed products as fast as possible to start harvesting the benefits.
DONE
ACCEPT TEST
WHO: Customers, Developers and Product Owner WHAT: Customer test the product, Developers fixes issues and Product Owner records any new ideas. WHY: To confirm that the developed products fits the purpose of the customer.
DONE
NEW IDEAS
WHO: Customers, Developers and Product Owner WHAT: Throughout the whole process everyone should be creative and enable idea generation. All ideas could turn into new pieces of work. New ideas are added to the Portfolio Kanban Board and ignite the flow starting with the Idea activities. WHY: To capture any relevant ideas to enhance the product.
DONE
GLOSSARY
SCRUM MASTER
SCALING
PORTFOLIO KANBAN BOARD
CUSTOMER
SCRUM
PRODUCT OWNER
AGILE MANIFESTO
DEVELOPERS
AGILE MINDSET