SlideShare a Scribd company logo
codaflex.com
General Scrum Guidelines
for Everyday Activates
by
Teddy Piperkova
July2021
General Scrum Guidelines
2 | P a g e
Before Sprint Starts
• List of PBIs (Product Backlog Items) – clean and prioritized. It is good to keep the Committed
task on top of your list. Remember, each PBI need to have proper State and Assignee.
• Plan your resources even if you did not have time for Backlog Grooming and prioritization. Do
not start planning before you discussed with the other POs (Product Owners) your team’s
capacity for the Sprint.
• Book a room for your Sprint Planning meeting in advance.
Step-by-step Sprint Planning
• Always start with Retrospective as it is important to receive feedback from the team on what
went well and what went wrong.
• Start by creating new Sprint, using name that represents Sprint duration (for example, Apr 16 –
Apr 27, 2022). Be consistent. Think of developers that are part of several teams.
• Try to use two-week Sprints, if you have enough work planned for that duration.
• Clean up the old Sprint from remaining PBIs before moving new items from the Backlog. Use
the new Sprint to create tasks for old PBIs. Do not reopen Done PBIs to create new tasks.
• Decompose PBIs into tasks, which are part of your Sprint.
• Assign and estimate tasks together with the developers. Let people add their own input and do
estimations for themselves.
• You are done with Sprint Planning when you reach the team’s capacity.
• Schedule your Daily Stand-up meetings once your done with the planning by sending a calendar
invitation.
Daily Stand-up Format
• Always start on time! Even if different members of the team are still not in the meeting. They
can catch-up afterwards through the system or by a quick one-on-one discussion.
• If there is a meeting conflict, reschedule it but do not skip it.
• Try to hold the meetings outside the developers’ room. You do not want to distract others
while having this meeting.
• Keep it short by standing during the meeting. If you feel too comfortable, it may take longer
than needed.
• Remember that anybody can be a Presenter! There are no specific roles and each team
member should provide update on their personal tasks and progress.
• Go through the three questions format and keep it quick, avoiding technical talk. If needed,
technical discussions go after the meeting.
• Have an action plan for the Blocked tasks before leaving the room.
Additional Sprint Activities
• Have regular Backlog Grooming by adding all project related work into VSTS. Also, add detailed
descriptions to the PBIs and use information from the Bug Reporting Template when creating
issues.
• When you complete a task that is In Progress move it to Done. There is no need to wait for the
Daily Stand-up.
General Scrum Guidelines
3 | P a g e
• For tasks that have remaining work after the end of the day, decrease the estimated time
accordingly.
• If you have finished your tasks for the day, get some tasks from the To Do.
• Use the discussion field if you have any comments or questions to others.
• PBIs are assigned and closed by the POs.
• When at capacity and you receive a change request, add a new item but remove something
else that is already part of the Sprint. The removed task can be moved to a future Sprint or
return to the PBI list, depending on its priority. Do not forget to change its State too.
Sprint Wrap-up
• Try to have a Review session every few Sprints when you have enough things to share. This
allows exchange of ideas and successes.
• Each developer needs to prepare a list of Items that can be presented on the Review meeting.
• Try to fit each presentation in five minutes.
Most important of all is to remember – Schedule your meetings and be always on time!
***
This document is part of a set, which Codaflex distributes when our Agile Coaches
help clients with the implementation of Agile and Scrum processes.
For more information, go to our website or contact us at info@codaflex.com.

More Related Content

What's hot

Scrum overview
Scrum overviewScrum overview
Scrum overview
Paul Nil
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
barrst
 

What's hot (20)

Scrum Guidelines
Scrum GuidelinesScrum Guidelines
Scrum Guidelines
 
Scrum overview
Scrum overviewScrum overview
Scrum overview
 
Sprint review and Retrospective
Sprint review and RetrospectiveSprint review and Retrospective
Sprint review and Retrospective
 
Scrum checklist
Scrum checklistScrum checklist
Scrum checklist
 
Agile SCRUM presentation HJT_Final
Agile SCRUM presentation HJT_FinalAgile SCRUM presentation HJT_Final
Agile SCRUM presentation HJT_Final
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Scrum Methodology
Scrum Methodology Scrum Methodology
Scrum Methodology
 
Another Scrum Cheat Sheet (great one pager)
Another Scrum Cheat Sheet (great one pager)Another Scrum Cheat Sheet (great one pager)
Another Scrum Cheat Sheet (great one pager)
 
Al Nelson on Project Management for Game Developers
Al Nelson on Project Management for Game DevelopersAl Nelson on Project Management for Game Developers
Al Nelson on Project Management for Game Developers
 
Scrum
ScrumScrum
Scrum
 
Beginners Guide to Scrum
Beginners Guide to ScrumBeginners Guide to Scrum
Beginners Guide to Scrum
 
What is scrum
What is scrumWhat is scrum
What is scrum
 
Scrum mastery
Scrum masteryScrum mastery
Scrum mastery
 
Scrum Framework
Scrum FrameworkScrum Framework
Scrum Framework
 
Scrum rules
Scrum rulesScrum rules
Scrum rules
 
Scrum (2)
Scrum (2)Scrum (2)
Scrum (2)
 
Scrum methodology
Scrum methodologyScrum methodology
Scrum methodology
 
Agile Resort Brochure Game July 2011
Agile Resort Brochure Game July 2011Agile Resort Brochure Game July 2011
Agile Resort Brochure Game July 2011
 
Resort brochure game
Resort brochure gameResort brochure game
Resort brochure game
 
Scrum introduction
Scrum introductionScrum introduction
Scrum introduction
 

Similar to General Scrum Guidelines - Everyday Activities

FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
duhitha2
 

Similar to General Scrum Guidelines - Everyday Activities (20)

Guideline for retrospective & sprint planning
Guideline for retrospective & sprint planningGuideline for retrospective & sprint planning
Guideline for retrospective & sprint planning
 
Teaching Scrum Fundamentals_A Quick Guide to Getting Started.pdf
Teaching Scrum Fundamentals_A Quick Guide to Getting Started.pdfTeaching Scrum Fundamentals_A Quick Guide to Getting Started.pdf
Teaching Scrum Fundamentals_A Quick Guide to Getting Started.pdf
 
Teaching Scrum Fundamentals_A Quick Guide to Getting Started.pdf
Teaching Scrum Fundamentals_A Quick Guide to Getting Started.pdfTeaching Scrum Fundamentals_A Quick Guide to Getting Started.pdf
Teaching Scrum Fundamentals_A Quick Guide to Getting Started.pdf
 
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
 
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?"
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?"When Management Asks You: “Do You Accept Agile as Your Lord and Savior?"
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?"
 
Agile Scrum CMMI
Agile Scrum CMMIAgile Scrum CMMI
Agile Scrum CMMI
 
PMI-ACP Domain 1 Agile Principles and Mindset
PMI-ACP Domain 1 Agile Principles and MindsetPMI-ACP Domain 1 Agile Principles and Mindset
PMI-ACP Domain 1 Agile Principles and Mindset
 
Presentation on agile methodology
Presentation on agile methodologyPresentation on agile methodology
Presentation on agile methodology
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrum
 
Agile with scrum methodology
Agile with scrum methodologyAgile with scrum methodology
Agile with scrum methodology
 
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through Scrum
 
Scrum Overview
Scrum OverviewScrum Overview
Scrum Overview
 
Software Development Guide To Accelerate Performance
Software Development Guide To Accelerate PerformanceSoftware Development Guide To Accelerate Performance
Software Development Guide To Accelerate Performance
 
Rex Sprint 0 - how build the data model with 2 BA and 3 IT architects
Rex Sprint 0 - how build the data model with 2 BA and 3 IT architectsRex Sprint 0 - how build the data model with 2 BA and 3 IT architects
Rex Sprint 0 - how build the data model with 2 BA and 3 IT architects
 
Scrum Meetings Overview.pptx
Scrum Meetings Overview.pptxScrum Meetings Overview.pptx
Scrum Meetings Overview.pptx
 
ME135A Agile lean workshop101414
ME135A Agile lean workshop101414ME135A Agile lean workshop101414
ME135A Agile lean workshop101414
 
Scrum
ScrumScrum
Scrum
 
Adamson "Blueprint for Managing Your Project"
Adamson "Blueprint for Managing Your Project"Adamson "Blueprint for Managing Your Project"
Adamson "Blueprint for Managing Your Project"
 
Roadmap to Scrum Master ( CSM )
Roadmap to Scrum Master ( CSM ) Roadmap to Scrum Master ( CSM )
Roadmap to Scrum Master ( CSM )
 

General Scrum Guidelines - Everyday Activities

  • 1. codaflex.com General Scrum Guidelines for Everyday Activates by Teddy Piperkova July2021
  • 2. General Scrum Guidelines 2 | P a g e Before Sprint Starts • List of PBIs (Product Backlog Items) – clean and prioritized. It is good to keep the Committed task on top of your list. Remember, each PBI need to have proper State and Assignee. • Plan your resources even if you did not have time for Backlog Grooming and prioritization. Do not start planning before you discussed with the other POs (Product Owners) your team’s capacity for the Sprint. • Book a room for your Sprint Planning meeting in advance. Step-by-step Sprint Planning • Always start with Retrospective as it is important to receive feedback from the team on what went well and what went wrong. • Start by creating new Sprint, using name that represents Sprint duration (for example, Apr 16 – Apr 27, 2022). Be consistent. Think of developers that are part of several teams. • Try to use two-week Sprints, if you have enough work planned for that duration. • Clean up the old Sprint from remaining PBIs before moving new items from the Backlog. Use the new Sprint to create tasks for old PBIs. Do not reopen Done PBIs to create new tasks. • Decompose PBIs into tasks, which are part of your Sprint. • Assign and estimate tasks together with the developers. Let people add their own input and do estimations for themselves. • You are done with Sprint Planning when you reach the team’s capacity. • Schedule your Daily Stand-up meetings once your done with the planning by sending a calendar invitation. Daily Stand-up Format • Always start on time! Even if different members of the team are still not in the meeting. They can catch-up afterwards through the system or by a quick one-on-one discussion. • If there is a meeting conflict, reschedule it but do not skip it. • Try to hold the meetings outside the developers’ room. You do not want to distract others while having this meeting. • Keep it short by standing during the meeting. If you feel too comfortable, it may take longer than needed. • Remember that anybody can be a Presenter! There are no specific roles and each team member should provide update on their personal tasks and progress. • Go through the three questions format and keep it quick, avoiding technical talk. If needed, technical discussions go after the meeting. • Have an action plan for the Blocked tasks before leaving the room. Additional Sprint Activities • Have regular Backlog Grooming by adding all project related work into VSTS. Also, add detailed descriptions to the PBIs and use information from the Bug Reporting Template when creating issues. • When you complete a task that is In Progress move it to Done. There is no need to wait for the Daily Stand-up.
  • 3. General Scrum Guidelines 3 | P a g e • For tasks that have remaining work after the end of the day, decrease the estimated time accordingly. • If you have finished your tasks for the day, get some tasks from the To Do. • Use the discussion field if you have any comments or questions to others. • PBIs are assigned and closed by the POs. • When at capacity and you receive a change request, add a new item but remove something else that is already part of the Sprint. The removed task can be moved to a future Sprint or return to the PBI list, depending on its priority. Do not forget to change its State too. Sprint Wrap-up • Try to have a Review session every few Sprints when you have enough things to share. This allows exchange of ideas and successes. • Each developer needs to prepare a list of Items that can be presented on the Review meeting. • Try to fit each presentation in five minutes. Most important of all is to remember – Schedule your meetings and be always on time! *** This document is part of a set, which Codaflex distributes when our Agile Coaches help clients with the implementation of Agile and Scrum processes. For more information, go to our website or contact us at info@codaflex.com.