This document discusses principles of Agile and Modern Agile. It begins with an introduction by Daniel Heater, and then discusses criticisms of traditional Agile approaches that focus too heavily on certification, tools, and consultants. The remainder of the document focuses on Modern Agile principles like delivering value continuously, experimenting and learning rapidly, and making safety a prerequisite. It proposes using a survey approach where teams own the questions to discuss how these principles manifest in their work, with the goal of improving outcomes for customers rather than comparing scores between teams.

1. Return of the Principles

2. Who am I?
Daniel Heater
I get paid to develop software
I am a husband and father
I've been a student of Agile since 2005
I geek out on finding ways to do stuff
better

3. Able to move quickly and easily.
Agile:

4. What's wrong with old Agile?

5. Get your
cerification!
Hire ouR consultants!!
$$$ Buy our tool to $$$
make your team Agile!
* Not all consultants are bad, but beware of unrealistic promises from them
and unrealistic expectations from your organization.

6. Team,
These are the non-negotiables regarding our Scrum
Sessions.
Each Sprint to run on a 2wk cycle
Backlog Grooming
To occur at least once per Sprint
Product Owner to lead supported by Scrum Master
& Team Members as required including relevant
stakeholders if deliverables go to another team.
To occur prior to Sprint Planning (have backlog groomed
prior to Sprint Planning)
Includes Prioritization and T-Shirt estimates
Includes known backlog items to complete project
Sprint Planning
To occur at beginning of each Sprint Cycle
Includes all team members
Stories are to be estimated using Fibonacci Sequence of
1,2,3,5,8,13
Planning should include estimates for Spikes or Interrupts
as appropriate
Each story to have a definition of ‘Done’ included in
description
Facilitated by Scrum Master
Dependencies clearly defined and communicated to the
dependent scrum team for their sprint planning
Daily Standups
Occurs at the same time & same location each day
Standups to be limited to 15 minutes
Standups are ‘Facilitated’ by the Scrum Master NOT ‘Lead’ by the
Scum Master
Team members each provide input at the standup
Jira updates should be completed prior to the standup (with the
exception of moving task to Done)
Standups are to report Work Completed, Work to Be Performed
and Blockers
Standups are NOT to include In Depth Technical Discussions (No
Problem Solving)
In Depth Technical Discussions and Problem Solving may occur
following the Stand Up
Sprint Review
Managers will establish Sprint Review Format (may include demo)
Sprint Review to occur at what is now the Bi-Weekly Project
Reviews
Includes all team members (Product Owner will speak for team)
Sprint Review will be a 10 minute block
Sprint Review will conclude with a brief Project Review (inside the
10 minute window) (Project Manager/Scrum Master will present)
Retrospective
To occur at the end of each Sprint Cycle
Includes all team members
Focus includes:
- What worked well for the team
- What did not work well for the team
- What can the team do different to improve velocity
- What can the business do different to remove impediments
Contents of Retro to be recorded and stored in a shared location
Command & Control
NOT AGILE
Not Cool!!
In Agile, everything is negotiable!!

9. So How Do I Get Started
with Modern Agile?

12. Survey Ground Rules
This is a “Whose line is it anyway survey?” The questions are
made up and the points don’t matter.
The intent is to get people talking about Modern Agile Principles
and how they manifest in your team.
The team should own the survey. The team should
add/delete/change questions as they see fit.
If you are using this instrument to figure out if you team is
“good” or comparing scores with other teams
You’re doing it wrong!

13. Make People Awesome
Do we delight our customers?
Do we have an appropriate degree of autonomy?
Do we have a well understood sense of purpose?
Do business and product development people work as one team?

14. Deliver Value Continuously
Do we deliver meaningful outcomes frequently?
Is our primary measure of progress outcomes for our customers?
Do we value delivering sooner over keeping busy?
Are we minimizing friction?

15. Experiment & Learn Rapidly
Do we make time to improve our craftsmanship?
Do we validate our ideas with simple minimal viable products?
Are we able to get feedback rapidly?
Is knowledge shared broadly?

16. Make Safety a Prerequisite
Do we catch mistakes before they get to customers?
Can we make changes without fear?
Is it safe to expose your ignorance?
Do others have your back?

17. Able to move quickly and easily.
Agile:

19. Modern Agile graphics from the Modern Agile media kit licensed under Creative
Commons Attribution-ShareAlike License
Thanks to:
The Modern Agile Slack community.
Dan Petrek for inspiring the Modern Agile survey idea.
John Cutler for suggesting team ownership of the survey.
Sandy Mamoli whose principle cards at nomad8.com inspired some of the survey
questions.
Joshua Kerievsky - The madman behind modern Agile.
This presentation is licensed under a Creative Commons Attribution-ShareAlike 4.0
International License.