One of the co-founders of scrum has said it takes “two minutes to learn, but a lifetime to master”. In this session, Kathy will cover what Agile Scrum actually IS and how you can benefit from using it in your projects. She’ll cover the basic concepts (duration will be slightly longer than two minutes). She will also show you how to avoid common Agile nightmares. Kathy will compare Agile to other project management techniques and demonstrate why Agile is better for you, your stakeholders, your boss, and ultimately your end users. Kathy promises the session will be shorter than the average lifetime in duration.
Scaling API-first – The story of a global engineering organization
2 Minutes to Learn, A Lifetime to Master - Agile Scrum for Collaboration
1. Two Minutes To Learn,
A Lifetime To Master
– Agile Scrum for Collaboration
• Kathy Brown, PSC Group
2. Who am I?
• Kathy Brown
• Senior Consultant at PSC Group
• Certified Professional Scrum Master
• IBM Champion
• kathy@runningnotes.net
• www.Iamkathybrown.com
• @katheager
3. What are we talking about?
• What IS Agile?
• What are the benefits?
– aka Why you care
• Who? The Roles
• When? The Events
• How? Artifacts and Tools
4. $50 to buy dinner
• Agile
– Buy a nice dinner to make at
home
• I want to have steak
• I want to have wine with dinner
• I want to have a side dish
• Waterfall
– Buy filet mignon, 2 filets, $30
– Buy Bread and Butter wine
for $15
– Buy green beans, $5
• What happens when…
– The store is out of filet mignon or the filet looks terrible or is too
expensive
– At the store you decide you also want dessert
5. What is Agile?
• Framework
– Iterative
– Incremental
– Prioritized
– Value Delivery
Scrum (n): A framework within which people can address complex adaptive problems,
while productively and creatively delivering products of the highest possible value.
6. What are the benefits?
• Transparency Trust
• Predictability
• Adaptability
• Satisfaction
– Early and frequent feedback
7. Who? The Roles
• Product Owner
• Scrum Master
• Development Team
• Ideal team is 6-9 people
• Stakeholders (Not part of the team)
8. When? The Events
• The Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
9. How? The Artifacts and Tools
• Product Backlog
– Epics
– Features
– User Stories
• Acceptance Criteria
• Definition of Done
– Tasks
• Sprint Backlog
• Scrum Board
• Story Points
• Velocity and Burn Down
Later add I want to have dessert
Prioritize I HAVE to have wine
While in the meat dept I change my mind and can adapt my dessert and side dish
Buy cheesecake, $10
Anyone here work on an “agile” project?Why was it Agile? Someone said it was? 2 week “sprints”? Daily stand ups?
Cherry picking low hanging
Richard adjust and adapt
Example – “what does he do all day?”
NIGHTMARE – micromanagement
NIGHTMARE – schedule gets further and further off, waterfall
Scrum master should be FACILITATING
NIGHTMARE – Too many cooks
NIGHTMARE – hour long scrums
NIGHTMARE – too many meetings outside of these with too many people
NIGHTMARE: overly large user stories, CHANGING user stories
NIGHTMARE: “bad” burndown