Your SlideShare is downloading. ×
0
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Hands-on practice: two ways to run a project
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Hands-on practice: two ways to run a project

599

Published on

We're talking about different ways and frameworks and methodologies on how to make a project successful. …

We're talking about different ways and frameworks and methodologies on how to make a project successful.

Well, let's stop talking and try two different approaches - plan-driven and change-driven. Let's do it with a some practical tasks and then discuss what happens and why in the good company.

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

  • Be the first to like this

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Hands-on practice:two ways to run a projectThe Ball-Point Game Reloaded
  • 2. The Ball-Point GameFacts:○ game author is Boris Bloger○ introduced at Spring Scrum Gathering 2008 in Chicago by Tobias Mayer○ simulates Scrum process
  • 3. How it looks like?Team members pass the ballsamongst the whole team.When the ball goes throw all teammembers it is produced.
  • 4. RulesThe basic rules are:○ The balls must have air time○ Balls that hit the floor don’t count, and have to be returned to the starting point to get them back in play○ No balls to your direct neighbour○ Start point = End point (i.e. the container)○ Iteration = 2 minutes○ In between = 1 minute, to review and plan○ Play 5 iterations
  • 5. What we are going to do?Agenda:● simulate plan-driven approach● simulate change-driven approach● analyze lessons learned
  • 6. So we needtwo sets of rules for two different approaches!
  • 7. Making teams
  • 8. Rules for plan-driven approachAdditional rules for plan-driven approach:● Number of balls to use is predefined● Number of balls to be produced is predefined● Planning phase: 3 min● Production phase: 3 min● Review: 1 min
  • 9. Rules reloadedThe basic rules are:○ The balls must have air time○ Balls that hit the floor don’t count, and have to be returned to the starting point to get them back in play○ No balls to your direct neighbour○ Balls must be touched by hand○ The ball is produced when it passed through all team members○ Teams can use whatever it wants during the production phase○ The team can not change its process during production phase○ Teams are accountable for counting the produced balls quantity
  • 10. Plan-driven approachretrospective● What happened?● Did you want to change the process?● What will happen if the production phase lasts for 15 minutes?
  • 11. Making new teams
  • 12. Rules for change-drivenapproachRules for change-driven approach:● Team can use as much balls as it likes● Team defines the quantity of balls it is committed to produce● Planning phase: 1 min● Production phase: 1 min● Review: 1 min● Play 3-5 iterations
  • 13. Rules reloadedThe basic rules are:○ The balls must have air time○ Balls that hit the floor don’t count, and have to be returned to the starting point to get them back in play○ No balls to your direct neighbour○ Balls must be touched by hand○ The ball is produced when it passed through all team members○ Teams can use whatever it wants during the production phase○ The team can not change its process during production phase○ Teams are accountable for counting the produced balls quantity
  • 14. Change-driven approachretrospective● And what happened at this time?● Did you want to change the process?● Did you change it? How?● What was the iteration that felt great?
  • 15. Lessons learnedWhat did you learn today? … Fill it by yourself!
  • 16. But think about…● What made the teamwork?● How time pressure affects the team?● How did you improve as a team?● In what simulation production process is more cost effective?● Why the team began to show more predictable result?
  • 17. Deming cycleIs it better to havea long feedback loop ora short one?
  • 18. LinksThe Classic Ball-Point Game description:● http://goo.gl/NfHhd● http://goo.gl/r6QnuDeming Cycle:● http://en.wikipedia.org/wiki/PDCAScrum:● http://www.scrum.org/scrumguides
  • 19. ContactsLeave feedback: http://meetu.ps/dvJCnContact me: http://about.me/NetRatRate me: http://spkr8.com/t/12711
  • 20. CreditsMaterials used in the presentation:● photo by Adrian Cockle● Wikipedia: http://www.wikipedia.org/● Open Clip Art Library: http://openclipart.org/
  • 21. Thank You!

×