0
Talk
Scrumify
@
November 2012
Who am I?
Pedro Gustavo Torres
Graduation in 2002 and Master in 2008
> 10 years of experience in IT industry
> 6 years dev...
Overview
What is Agile?
What is Scrum?
Waterfall Model vs Scrum
Scrum Roles
Backlogs
Estimates
A normal Scrum Project
Scru...
What is Agile?
What is Agile?
Set of Principles:
respect for the worth of every person
truth in every communication
transparency of all d...
Agile Manifesto
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Cu...
What is Scrum?
What is Scrum?
Framework
Prescription
Tool
Iterative based
Inspect and adapt
Two perspectives:
– The art of the possible (...
Sprints
Time boxed
2 to 4 weeks (recommended)
Features defined (closed)
100% tested features delivered
Tracking:
– Task (w...
Task (white) board
What is Scrum?
Burndown chart
What is Scrum?
Waterfall Model vs Scrum
Waterfall Model vs Scrum
Waterfall:
– Fixed features
– Variable Cost and Time
– Imposes a sequence of events
Scrum:
– Fixe...
Scrum Roles
Scrum Roles
Customers/Stakeholders
Product Owner
ScrumMaster
Core Team
Customers/Stakeholders
Owns the vision
They know what they need but normally they tell you
what they want
Must be availabl...
Product Owner
Provides Customer and Business support and Product
guidance
Embraces and nurtures the customer's vision
Main...
ScrumMaster
Builds and maintains healthy teams
Works with the team all the time
Doesn't tell the team what to do
Conducts ...
Core Team
5-7 members (preferably)
Cross-functional
Empowered:
– Estimates
– Pull work
– Suggest stories to the customers ...
Backlogs
Backlogs
Product Backlog
Sprint Backlog
Product Backlog
Living Document
– Key for deliver value to the customer
– Defined in Sprint zero, in Grooming Meetings and...
Sprint Backlog
User stories that are going to be developed during the
sprint
– Example: “As a user I can see my billing hi...
Estimates
Estimates
Units for stories:
– Story points
– Ideal days
– T-shirt sizes
Units for tasks:
– Hours
Techniques:
– Planning p...
Planning Poker
Choose references and use comparison
No scales or units defined (agnostic):
– Fibonacci sequence (recommend...
Planning Poker
Estimates
A normal Scrum Project
Sprint zero
Planning meeting
Daily Scrums
Grooming meeting
Demo
Retrospective
Release
A normal Scrum Project
Sprint zero
Preparation of the project
Building of the Product backlog
– Identifying user stories
– Prioritize
Definition ...
Planning meeting
Choosing which user stories are going to be done during
the sprint:
– Prioritization of the PB
– Team's V...
Daily Scrums
Ideally first thing in the morning
Everyone talks to the team not to the ScrumMaster
No more than 15 minutes
...
Grooming Meeting
Maintenance of the Product Backlog
Re-estimating (or dropping) old stories
Estimating new stories (that m...
Demo
Demonstration of the implementation of the user stories
to the customers/stakeholders
Ideally all the team is in the ...
Retrospective
Meeting without the PO
Questions:
– What are we doing well?
– What can be better?
– What should we start/sto...
Release
When should we release?
– At the end of each sprint?
– Once a month?
Always double-check the DoD (Definition of Do...
Scrum of Scrums
Scrum of Scrums
Scaling Scrum to large project teams
Clusters of teams to discuss their work
Each team designates one pers...
Scrum of Scrums
Personal stuff
Personal stuff
Never Ever Assume
– Ass | u | me
“Assumption is the mother of all fuckups” *
Being Agile is a state of mind...
The Waterfall model sometimes works. Scrum works more
often
Scrum is “apparently” more expensive on the short term
than th...
Scrum misfortunes
Naming “Sprints” to timeboxes
“Working Software over Comprehensive Documentation”
Hard to accommodate ro...
ScrumMaster is a full time job
Scrum is the art of the possible
– Use (if possible) the prescription of Scrum for a few sp...
“A great team will have great success with or without
Scrum. A shitty team will still produce shit with scrum.
Just that t...
Trouble sleeping?
A few suggestions:
Personal stuff
Blog: pedrogustavotorres.com
Email: pedro.gustavo.torres@gmail.com
Twitter: twitter.com/_pedro_torres
My contacts
Personal...
Upcoming SlideShare
Loading in...5
×

Scrumify :: Porto Linux 2012

783

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
783
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Scrumify :: Porto Linux 2012"

  1. 1. Talk Scrumify @ November 2012
  2. 2. Who am I? Pedro Gustavo Torres Graduation in 2002 and Master in 2008 > 10 years of experience in IT industry > 6 years developing > 4 years managing projects > 2 years scrumming Companies worked with: Certifications held:
  3. 3. Overview What is Agile? What is Scrum? Waterfall Model vs Scrum Scrum Roles Backlogs Estimates A normal Scrum Project Scrum of Scrums Personal stuff
  4. 4. What is Agile?
  5. 5. What is Agile? Set of Principles: respect for the worth of every person truth in every communication transparency of all data, actions, and decisions trust that each person will support the team commitment to the team and to the team’s goals and Practices: – Scrum – Extreme Programming (TDD, Pair Programming, etc.) – Kanban – ...
  6. 6. Agile Manifesto Individuals and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to Change over Following a Plan While there is value in the items on the right we value the items on the left more What is Agile?
  7. 7. What is Scrum?
  8. 8. What is Scrum? Framework Prescription Tool Iterative based Inspect and adapt Two perspectives: – The art of the possible (adaptative) – ScrumBut is killing the game (strict)
  9. 9. Sprints Time boxed 2 to 4 weeks (recommended) Features defined (closed) 100% tested features delivered Tracking: – Task (white) board – Burndown chart What is Scrum?
  10. 10. Task (white) board What is Scrum?
  11. 11. Burndown chart What is Scrum?
  12. 12. Waterfall Model vs Scrum
  13. 13. Waterfall Model vs Scrum Waterfall: – Fixed features – Variable Cost and Time – Imposes a sequence of events Scrum: – Fixed time and cost – Variable features – Cross-functionality
  14. 14. Scrum Roles
  15. 15. Scrum Roles Customers/Stakeholders Product Owner ScrumMaster Core Team
  16. 16. Customers/Stakeholders Owns the vision They know what they need but normally they tell you what they want Must be available to attend meetings: – with the PO to look at the Product Backlog – with all the team (preferably) to assist at the demo at the end of each sprint Scrum Roles
  17. 17. Product Owner Provides Customer and Business support and Product guidance Embraces and nurtures the customer's vision Main responsibility to identify the stories of the project that goes to the product backlog Full time job Commits with the customer Represents the customer's interest Needs business background “The bad cop” Scrum Roles
  18. 18. ScrumMaster Builds and maintains healthy teams Works with the team all the time Doesn't tell the team what to do Conducts the scrum meetings Facilitator Helps the teams achieve is goals (focus) Full time job Doesn't need technical background “The good cop” Scrum Roles
  19. 19. Core Team 5-7 members (preferably) Cross-functional Empowered: – Estimates – Pull work – Suggest stories to the customers / stakeholders Commits with the PO through the sprint backlog Scrum Roles
  20. 20. Backlogs
  21. 21. Backlogs Product Backlog Sprint Backlog
  22. 22. Product Backlog Living Document – Key for deliver value to the customer – Defined in Sprint zero, in Grooming Meetings and Meetings between the PO and the customer – Everyone can add stories to the PB The items are: – rated as Stories, Themes or Epics – ordered by priority – measured in Story points (preferably) INVEST on the user stories: – Independent, Negotiable, Valuable, Estimable, Small and Testable Backlogs
  23. 23. Sprint Backlog User stories that are going to be developed during the sprint – Example: “As a user I can see my billing history by month so that I can download the invoices” Tasks – Hours – Acceptance criteria Defined in the scrum planning meeting Backlogs
  24. 24. Estimates
  25. 25. Estimates Units for stories: – Story points – Ideal days – T-shirt sizes Units for tasks: – Hours Techniques: – Planning poker
  26. 26. Planning Poker Choose references and use comparison No scales or units defined (agnostic): – Fibonacci sequence (recommended): 1, 2, 3, 5, 8, 13, 21... Everyone draws a card at the same time Advantages: – Prevents slacking – Engagement – Fun Disadvantages: – Time consuming Estimates
  27. 27. Planning Poker Estimates
  28. 28. A normal Scrum Project
  29. 29. Sprint zero Planning meeting Daily Scrums Grooming meeting Demo Retrospective Release A normal Scrum Project
  30. 30. Sprint zero Preparation of the project Building of the Product backlog – Identifying user stories – Prioritize Definition of Done (task, sprint, release, etc.) A normal Scrum Project
  31. 31. Planning meeting Choosing which user stories are going to be done during the sprint: – Prioritization of the PB – Team's Velocity A normal Scrum Project
  32. 32. Daily Scrums Ideally first thing in the morning Everyone talks to the team not to the ScrumMaster No more than 15 minutes Deeper issues stay off Standing meeting: – What did you do yesterday? – What are you going to do today? – Do you have any problems? A normal Scrum Project
  33. 33. Grooming Meeting Maintenance of the Product Backlog Re-estimating (or dropping) old stories Estimating new stories (that might show up) A normal Scrum Project
  34. 34. Demo Demonstration of the implementation of the user stories to the customers/stakeholders Ideally all the team is in the room The demo should be done by the Product Owner or by the Customer himself A normal Scrum Project
  35. 35. Retrospective Meeting without the PO Questions: – What are we doing well? – What can be better? – What should we start/stop doing? Voting on the relevant issues A normal Scrum Project
  36. 36. Release When should we release? – At the end of each sprint? – Once a month? Always double-check the DoD (Definition of Done) list A normal Scrum Project
  37. 37. Scrum of Scrums
  38. 38. Scrum of Scrums Scaling Scrum to large project teams Clusters of teams to discuss their work Each team designates one person to also attend a scrum of scrums meeting Questions: – What has your team done since we last met? – What will your team do before we meet again? – Is anything slowing your team down or getting in their way? – Are you about to put something in another team’s way?
  39. 39. Scrum of Scrums
  40. 40. Personal stuff
  41. 41. Personal stuff Never Ever Assume – Ass | u | me “Assumption is the mother of all fuckups” * Being Agile is a state of mind Doing Scrum isn't the goal... delivering great software is It takes (a lot of) time to assimilate story points Never tried planning poker (but the Fibonacci sequence works pretty well) * Everett McGillin in Under Siege 2
  42. 42. The Waterfall model sometimes works. Scrum works more often Scrum is “apparently” more expensive on the short term than the Waterfall model Changing minds is hard... habits even harder Scrum works great with Kanban Maintaining the Scrum framework isn't a piece of cake ScrumBut & WaterfallBut Personal considerations Personal stuff
  43. 43. Scrum misfortunes Naming “Sprints” to timeboxes “Working Software over Comprehensive Documentation” Hard to accommodate room for urgent bugs Story points backfired – Comparing team performances – Selling the unit of measure The term “Velocity” Scrum as a silverbullet Personal stuff
  44. 44. ScrumMaster is a full time job Scrum is the art of the possible – Use (if possible) the prescription of Scrum for a few sprints – Then adapt the framework to your reality – Vanilla Scrum is great but you can make your own flavor You MUST engage your customer: – Commitment (availability) – Scrum ceremonies You can’t fit Scrum in your team? Try Kanban! Takeaways Personal stuff
  45. 45. “A great team will have great success with or without Scrum. A shitty team will still produce shit with scrum. Just that the shitty scrum team will see it earlier than the shitty no-scrum team” Unknown source Food for thought Personal stuff
  46. 46. Trouble sleeping? A few suggestions: Personal stuff
  47. 47. Blog: pedrogustavotorres.com Email: pedro.gustavo.torres@gmail.com Twitter: twitter.com/_pedro_torres My contacts Personal stuff
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×