This document discusses the importance of team charters and definitions of ready and done in Agile development. It defines key elements of a team charter such as goals, success criteria, constraints, and team rules/working agreements. It also explains what a definition of ready and definition of done are, providing examples of criteria that could be included in each. The document emphasizes that definitions of ready and done are not static and should be informed by the team's experience. It poses questions about why teams should create charters and who is accountable for ensuring teams follow their charters.

1. Are We Done Yet?
Team Charter, Definition of Ready, Definition of Done

2. • Agile trainer and coach
• Member of PMI, Scrum Alliance,
Agile Alliance, Agile Leadership
Network
• CST, CSM, CSPO, CSP, PMI-ACP,
PMP
• Founder & executive committee
member of Agile Delivery for
Agencies, Programs, and Teams
(ADAPT)
• Experience in Federal and
commercial Agile transformations
Richard Cheng
richard.cheng@excella.com
@RichardKCheng

3. Scrum Overview
Product Vision
Roadmap
Day
Sprint…
…
…
Plan
Day
Day
Daily Scrum
Review
Retro
Sprint
Plan
Review
Retro
Idea
Initiation Release
Plan
Release Release
Plan
Plan
Time

4. Project Charter – Top down driven document
Team Charter – Team created working agreements

5. Project Charter Team Charter

6. Project Charter Team Charter
• Goals
• Success Criteria
• Constraints
• People and
resources
• Milestones
• Project
understanding
• Team rules /
working
agreements
• Schedule
• Definition of
Ready
• Definition of Done

7. What is the goal of this session?

8. What are key team issues facing your team?
Think of working agreements to address these issues.

9. Sprint Schedule

10. Software from requirements to production

11. Ready to start
PBI
Sprint
Release

12. • Defines when the Product Backlog Items are ready for the
team to consume
• Use INVEST as a guide
• Sample:
– Story defined and written
– Story traceable to source document (where appropriate)
– Acceptance criteria defined
– Dependencies identified
– Size estimated by delivery team
– User experience included (where appropriate)
– Performance criteria identified (where appropriate)
– Person who will accept the user story is identified
– Team has a good idea about how to demo the user story
Definition of Ready

13. Product Backlog Refinement
PBI
PBI
PBI
PBI
Add
Split
Reorder
Remove
High priority
to
next Sprint
Granularity
Fine
Coarse
Product Backlog
Reorder

14. • DoD is a checklist of valuable activities
required to produce software.
• DoD is the primary reporting mechanism
for team members.
• DoD is informed by reality.
• DoD is not static.
• DoD is an auditable checklist.
*from Dhaval Panchal, http://www.scrumalliance.org/articles/105-what-is-
definition-of-done-dod
Definition of Done*

15. Definition of Done
Definition of Done for the PBI
Security
Testing
Browser
Tested
Stress
Testing
Acceptance
Criteria
Definition of Done for the Sprint
Definition of Done for the
Release

16. Definition of Done
Definition of Done for the PBI
Definition of Done for the Sprint
Definition of Done for the
Release
Security
Testing
Browser
Tested
Stress
Testing
Acceptance
Criteria

17. Why should we create a team charter?
Who is accountable to making sure the team follows the
team charter?

18. Excella Consulting
Experience and Expertise in Agile Solutions
– Coaching
– Training
– Assessments
– Agile Adoption
– Agile Development Teams
– Agile PMO
Training Courses
– Certified ScrumMaster (CSM)
– Certified Scrum Product Owner (CSPO): The Agile Business Analyst
– Advanced Certified Scrum Product Owner (CSPO)
– Certified Scrum Developer (CSD)
– Agile Testing
– Agile Business Intelligence and Data Warehousing
– Automated Acceptance Testing – Great for Analysts and Testers!!
See http://www.excella.com/training for more information

19. Contact Information
Richard K Cheng
richard.cheng@excella.com
703-967-8620
http://www.excella.com
Twitter: @RichardKCheng