Save Your Team from the Template Zombie Apocalypse!

32 Pages·2016·1.77 MB·English

by  Krista Trapani

Save Your Team from the Template
Zombie Apocalypse!
Angela Johnson, PMP, PMI-ACP, CST
Certified Scrum Trainer & Agile Transformation Coach
http://collaborativeleadershipteam.com
@AgileAngela
Angela Johnson
PMP, PMI-ACP, CST
• 21+ years Information Technology with
traditional SDLC and Scrum/Agile
• Scrum Alliance:
 Trainer Approval Committee
 CSM Learning Objectives Team
 Agile Leadership Added Qualification Team
• Volunteer Facilitator PMI-MN Agile
Practitioner Community
• Based in Minneapolis, MN
2
©2016 Collaborative Leadership Team
Learning Objectives
• Beginning with Customer Collaboration,
Conversation and Definition of Done
• Know when to STOP using the User Story
template
• Prevent yourself and others from turning into
template zombies, incoherently mumbling “As
a user, I want…”
3
©2016 Collaborative Leadership Team
Customer Collaboration
Conversation
Definition of Done
4
©2016 Collaborative Leadership Team
Agile Manifesto
Agile Software Development Manifesto
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.
http://agilemanifesto.org
5
©2016 Collaborative Leadership Team
Agile Manifesto Principles
1 Our highest priority is to satisfy the customer 7 Working software is the primary measure of
through early and continuous delivery of progress.
valuable software.
8 Agile processes promote sustainable
2 Welcome changing requirements, even late development.
in development. Agile processes harness The sponsors, developers, and users should
change for the customer's competitive be able to maintain a constant pace
advantage. indefinitely.
3 Deliver working software frequently, from a 9 Continuous attention to technical excellence
couple of weeks to a couple of months, with and good design enhances agility.
a preference to the shorter timescale.
10 Simplicity--the art of maximizing the amount
4 Business people and developers must work of work not done--is essential.
together daily throughout the project.
11 The best architectures, requirements, and
5 Build projects around motivated individuals. designs emerge from self-organizing teams.
Give them the environment and support
12 At regular intervals, the team reflects on
they need, and trust them to get the job
how to become more effective, then tunes
done.
and adjusts its behavior accordingly.
6 The most efficient and effective method of
conveying information to and within a
development team is face-to-face http://agilemanifesto.org/
conversation.
6
Are You Discouraging Conversation?
It’s possible to read the same document and
interpret it differently!
7
©2016 Collaborative Leadership Team
Start with Collaboration & Conversation
• Agile and Scrum do not start with a Document
• We start with the Conversation
• We capture the Results of the Conversation
• Agile and Scrum do not prescribe WHO does
this or HOW these are captured
“Fix Support Ticket 3001”
“Supervisors need to
correct Manual Cash
Count Errors”
“Upgrade to Flex 4.0”
“Let Patients get Test
Results Online”
8
©2016 Collaborative Leadership Team
How do you Know When You’re Done?
• Have you accounted for assumptions?
Constraints? Dependencies? Happy Path?
Sad Path?
• Can you describe what you think the end result
looks like?
• How do we know that we all agree on what
“done” is?
9
©2016 Collaborative Leadership Team
When do User Stories Come from Anyway?
• 1999 eXtreme Programming Explained: Kent Beck
• Emphasis is not talking about the system but simply
talking to the Customer and each other…a simple
telling of the story
• Once Acceptance Criteria is agreed upon, test
cases are written FIRST and code is generated
against the test until it passes
• If we need to write down the results of the
conversation that’s great!
• XP (or any Agile approach) does not prescribe
WHO or HOW this is done
10
©2016 Collaborative Leadership Team