6. Development Engineering Process
Object Orientation Automated Tests Agile, Lean, XP
SOLID Source Control Team Dynamics
Patterns Automated Builds Continuous Learning
Secure Coding
11. agile principles
We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
(2001) Kent Beck l Mike Beedle l Arie van Bennekum l Alistair Cockburn l Ward Cunningham l Martin Fowler l James Grenning l Jim Highsmith l Andrew Hunt l
Ron Jeffries l Jon Kern l Brian Marick l Robert C. Martin l Steve Mellor l Ken Schwaber l Jeff Sutherland l Dave Thomas
12. agile principles & practices
process framework scrum
technical engineering clean code tdd
automated unit test s.o.l.i.d. sonar
continuous integration (ci) code coverage
technical debt
22. Scrum is An Elegantly Simple Software Method
Three Roles
Product Owner
Scrum Master
Self-organizing teams
Three ceremonies
Sprint/Iteration Planning
Daily Scrum (Stand-Up) / debrief
Scrum
Sprint Review Meeting
Three Artifacts
Product Backlog
Sprint Backlog
Burn Down Chart
23. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Shippable Velocity
Release
24. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Velocity
25. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Velocity
26. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Velocity
27. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Shippable Velocity
Release
28. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Shippable Velocity
Release
29. Burn Down
Customer Needs
Daily Scrum SCRUM
(stand-up)
Product Owner
Team
Scrum Master
Sprint Definition of
Product 1 Month to 2 Weeks Done
Backlog Sprint Review
Definition of (including demo)
Ready
Retrospective
Sprint Planning Sprint
Backlog Burn Up
Shippable Velocity
Release
30. WAIT! What about …
Task boards, Information Radiators
Reducing Work In Progress, Time Boxing
Self Organization, Pull vs
Push, Empowerment, Continuous
Learning, Planning Poker, Story
Sizing, Velocity, Team Swarming…
32. Scrum Master Product Owner The Team
Represents the Does the work
Facilitates and
business interests ● self organizes ●
protects the process
● sets priorities ● owns sprint backlog
● removes team
owns the product ● dev, test, arch, DBA,
impediments ●
backlog BA, SME, etc ●
Scrum
51. Scrum Master Product Owner The Team
Represents the Does the work
Facilitates and
business interests ● self organizes ●
protects the process
● sets priorities ● owns sprint backlog
● removes team
owns the product ● dev, test, arch, DBA,
impediments ●
backlog BA, SME, etc ●
Scrum
53. Scrum Master Product Owner The Team
Represents the Does the work
Facilitates and
business interests ● self organizes ●
protects the process
● sets priorities ● owns sprint backlog
● removes team
owns the product ● dev, test, arch, DBA,
impediments ●
backlog BA, SME, etc ●
Scrum
54. Scrum Master Product Owner The Team
Represents the Does the work
Facilitates and
business interests ● self organizes ●
protects the process
● sets priorities ● owns sprint backlog
● removes team
owns the product ● dev, test, arch, DBA,
impediments ●
backlog BA, SME, etc ●
Scrum
56. product vision
represent the business
write stories
update stake holders
slice stories
meet with customers
groom the Product Backlog
prepare for Sprint Planning
57. product vision
represent the business
write stories
update stake holders
slice stories
meet with customers
groom the Product Backlog
prepare for Sprint Planning
58. product vision
represent the business
write stories
update stake holders
slice stories
meet with customers
groom the Product Backlog
prepare for Sprint Planning
59. product vision
write stories
meet with customers
prepare for Sprint Planning
60. product vision
write stories
meet with customers
prepare for Sprint Planning
61. product vision
write stories
meet with customers
prepare for Sprint Planning
62. product vision
write stories
meet with customers
prepare for Sprint Planning
65. Product Owner Team scales the role of
Product Owner to support multiple Scrum
teams with a single vision
Product Owner Team
scrum scrum scrum
66. In a Product Owner Team, the PO acts as a
coordinator or quarterback between all of the
players. This team supports the Scrum Team
67. The Product Owner Team works on their own
cadence, ensuring backlog grooming and story
readiness for the Scrum Team
68. The Team
Avg. Scrum Team Size 7±2
Everyone wears multiple hats
Everyone works within the Sprint Cycle to deliver
working software!
69. The Team
Avg. Scrum Team Size 7±2
Everyone wears multiple hats
Everyone works within the Sprint Cycle to deliver
working software!
83. reactive approach to remove
scrum of scrums cross team impediments
multiple product owners synchronizing
Coordination Team and proactively aligning backlogs
single PO working with supporting roles,
to support multiple scrum teams