• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Vladimirs Ivanovs - Goldilocks and the Three Bears
 

Vladimirs Ivanovs - Goldilocks and the Three Bears

on

  • 702 views

Creating a book is not a simple project however applying Agile principles to the process might make it much more easier to manage and give you better results. During the workshop we will create a ...

Creating a book is not a simple project however applying Agile principles to the process might make it much more easier to manage and give you better results. During the workshop we will create a children's book of "Goldilocks and the three bears" by using SCRUM techniques. You will get familiar with Product Backlog, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective. You will also stay awake as workshop requires your active participation, gives ability to have fun and engage your creativity.

This workshop have been delivered by me at such locations as Agile Tour Vilnius 2013 and IPMA Project Management congress 2013 in Dubrovnik... now also at StartUp Latvia and Agile Latvia.

Another name for this workshop is "Creating children's book with SCRUM". A nice workshop to feel the agile process in action.

Statistics

Views

Total Views
702
Views on SlideShare
627
Embed Views
75

Actions

Likes
0
Downloads
11
Comments
0

8 Embeds 75

https://twitter.com 33
http://www.meetup.com 16
http://www.linkedin.com 13
https://www.linkedin.com 7
http://tracks.roojoom.com 3
https://m.facebook.com&_=1387437364902 HTTP 1
http://m.facebook.com 1
https://www.facebook.com 1
More...

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Vladimirs Ivanovs - Goldilocks and the Three Bears Vladimirs Ivanovs - Goldilocks and the Three Bears Presentation Transcript

    • Vladimirs Ivanovs Mountain Goat Software, Source: http://www.usborne.com/catalogue/book/1~PB~PBF~3063/goldilocks-and-the-three-bears.aspx LLC
    • Mr.SPOCK Mountain Goat Software, LLC
    • What you can expect from me? Mountain Goat Software, LLC
    • Speaker Mountain Goat Software, LLC
    • P Mountain Goat Software, LLC
    • WOrkshOps Mountain Goat Software, LLC
    • Consulting Mountain Goat Software, LLC
    • Give Knowledge Mountain Goat Software, LLC Picture: personal photo archive
    • Traditional vs Agile PM • • • Plan-driven Emphasis on stable scope • • Most planning at start of project • Mountain Goat Software, LLC Change-driven Value Driven Delivery: Customer-valued prioritization. Relative prioritization, Incremental delivery. Frequent prototypes, demonstration Adaptive Planning: Iteration. Progressive elaboration. Less upfront planning. Planning throughout the project.
    • What do we want? Adopt Agile approach in the project Meet the project goal effectively! Mountain Goat Software, LLC
    • Stages of learning • • • • • Level 1: Shu (“obey”) Traditional wisdom — learning fundamentals, techniques. “Do this, don’t do that” Level 2: Ha ("detach", "digress") Breaking with tradition — finding exceptions to traditional wisdom, reflecting on their truth, finding new ways, techniques, and proverbs Level 3: Ri – ("leave", "separate“) Transcendence — there are no techniques or proverbs, all moves are natural We begin from 1st level We can achieve next level only by practice  Mountain Goat Software, LLC
    • Traditional Software Development Long, Large, Linear, Late Time to Market Lifecycle Deliverables 12 to 36 months Define MRD Mountain Goat Software, LLC PRD Code Tech spec Test Code Test plan Deploy Funct test Doc Train
    • The Project Managers Conflict: Successful Project Meet Schedule Granger – big cheese Mountain Goat Software, LLC No Change! Best Product Change! Conflict* Edwards - Customer
    • The PMConflict: Successful Project Meet Schedule Granger – big cheese Mountain Goat Software, LLC No Change! Who’s to blame? -The customer?  -The project manger?  -The way we build software?  Best Product Change! Conflict* Edwards - Customer
    • Project noise level Far from Agreement Requirements Anarchy Technology Far from Certainty Mountain Goat Software, LLC Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle. Simple Close to Certainty Close to Agreement Complex
    • We’re losing the relay race “The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.” Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game”, Harvard Business Review, January 1986. Mountain Goat Software, LLC
    • Scrum in 100 words • Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. • It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). • The business sets the priorities. Teams selforganize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint. Mountain Goat Software, LLC
    • Scrum origins • • • • Jeff Sutherland • • Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum Ken Schwaber • • • ADM Scrum presented at OOPSLA 96 with Sutherland Author of three books on Scrum Mike Beedle • Scrum patterns in PLOPD4 Ken Schwaber and Mike Cohn • Co-founded Scrum Alliance in 2002, initially within the Agile Alliance Mountain Goat Software, LLC
    • Scrum has been used by: •Microsoft •Yahoo •Google •Electronic Arts •Lockheed Martin •Philips •Siemens •Nokia •IBM •Capital One •BBC Mountain Goat Software, LLC •Intuit •Nielsen Media •First American Real Estate •BMC Software •Ipswitch •John Deere •Lexis Nexis •Sabre •Salesforce.com •Time Warner •Turner Broadcasting •Oce
    • Scrum has been used for: • • • • • • • • • Commercial software In-house development Contract development Fixed-price projects Financial applications ISO 9001-certified applications Embedded systems 24x7 systems with 99.999% uptime requirements the Joint Strike Fighter Mountain Goat Software, LLC • Video game development • FDA-approved, life-critical systems • Satellite-control software • Websites • Handheld software • Mobile phones • Network switching applications • ISV applications • Some of the largest applications in use
    • Characteristics • • • • • • Self-organizing teams Product progresses in a series of two-weeks/month “sprints” Requirements are captured as items in a list of “product backlog” No specific engineering practices prescribed Uses generative rules to create an agile environment for delivering projects One of the “agile processes” Mountain Goat Software, LLC
    • A bit of history Lean Manufacturing Principals Mass Production Lean Software Development Iterative Incremental Development Agile Waterfall Practices RUP Scrum XP Toyota Production System Implementation 1900 1950 Your team?  1980 1990 •1986: The New, New Product development Game •1993: First Scrum team created by Jeff Sutherland •1995: Scrum formalized by Jeff Sutherland & Ken Schwaber •1999: First XP book •2001: Agile Manifesto •2001: First Scrum book by Ken Schwaber & Mike Beedle •2003: Scrum alliance formed, certification program started Mountain Goat Software, LLC Thanks to Henrik Kniberg 2000
    • The Agile Manifesto–a statement of values Individuals and interactions over Process and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan Source: www.agilemanifesto.org Mountain Goat Software, LLC
    • Scrum 24 hours Sprint 2-4 weeks Sprint goal Return Cancel Return Coupons Gift wrap Gift wrap Cancel Product backlog Mountain Goat Software, LLC Sprint backlog Coupons Potentially shippable product increment
    • Putting it all together Image available at www.mountaingoatsoftware.com/scrum Mountain Goat Software, LLC
    • Agile Software Development Iterate, Increment and Innovate Time to Market 1 to 6 months Waterfall test Lifecycle Deliverables Waterfall 12 to 36 months Working, tested code on short cycles Mountain Goat Software, LLC Waterfall deploy Waterfall documentation
    • Sprints • Scrum projects make progress in a series of “sprints” • Analogous to Extreme Programming iterations • Typical duration is 2–4 weeks or a calendar month at most • A constant duration leads to a better rhythm • Product is designed, coded, and tested during the sprint Mountain Goat Software, LLC
    • Working in an Iteration Define Develop Accept Mountain Goat Software, LLC Fixed Time (Iteration) Fixed Resources Plan Story Card A Story Card B Story Card C Story Card D Story Card … Review Release Backlog
    • Sequential vs. overlapping development Requirements Design Code Test Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. Mountain Goat Software, LLC
    • Incorrect Sprint Operation DESIGN SPRINT Mountain Goat Software, LLC CODE SPRINT TEST SPRINT
    • Mountain Goat Software, LLC
    • Incorrect Sprint Operation DESIGN CODE SPRINT Mountain Goat Software, LLC TEST
    • Incorrect Sprint Operation DESIGN CODE TEST Mountain Goat Software, LLC
    • Correct Sprint Operation DESIGN CODE TEST SPRINT Mountain Goat Software, LLC
    • No changes during a sprint Change • Plan sprint durations around how long you can commit to keeping change out of the sprint Mountain Goat Software, LLC
    • Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
    • Product owner • Define the features of the product • Decide on release date and content • Be responsible for the profitability of the product (ROI) • Prioritize features according to market value • Adjust features and priority every iteration, as needed • Accept or reject work results Mountain Goat Software, LLC
    • The ScrumMaster • • • • • • Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences Mountain Goat Software, LLC
    • The team • Typically 5-9 people • Cross-functional: • • Programmers, testers, user experience designers, etc. Members should be full-time • May be exceptions (e.g., database administrator) • Ideally, no titles but rarely a possibility • Teams are self-organizing • Membership should change only between sprints Mountain Goat Software, LLC
    • Queue theory – push vs pull Pull Push FIMO First In Maybe Out Mountain Goat Software, LLC FIFO First In First Out
    • Intensity Intensity Waterfall Scrum Time Mountain Goat Software, LLC
    • Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
    • Product backlog • The requirements • A list of all desired work on the project • Ideally expressed such that This is the product backlog Mountain Goat Software, LLC • • each item has value to the users or customers of the product Prioritized by the product owner Reprioritized at the start of each sprint
    • Team capacity Product backlog Sprint planning meeting Sprint prioritization • • Business conditions Analyze and evaluate product backlog Select sprint goal Sprint goal Sprint planning • Current product • Technology • Mountain Goat Software, LLC Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours Sprint backlog
    • Sprint planning • • • Team selects items from the product backlog they can commit to completing Sprint backlog is created • • Tasks are identified and each is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster High-level design is considered As a vacation planner, I want to see photos of the hotels. Mountain Goat Software, LLC Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
    • The daily scrum • Parameters • Daily • 15-minutes • Stand-up • Not for problem solving • Whole world is invited • Only team members, ScrumMaster, product owner, can talk • Helps avoid other unnecessary meetings Mountain Goat Software, LLC
    • Everyone answers 3 questions What did you do yesterday? What will you do today? Is anything in your way? 1 2 3 • These are not status for the ScrumMaster • They are commitments in front of peers Mountain Goat Software, LLC
    • Game schedule 00:05 Presentation on Product Backlog, Sprint Planning, Daily Scrum 00:10 Sprint Planning (decide how much to do) 00:11 Day 1 in Sprint 1 (work) 00:15 Daily Scrum in Sprint 1 (what did you do, what will you do, obstacles) 00:16 Day 2 in Sprint 1 (work) Mountain Goat Software, LLC
    • Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
    • The sprint review • Team presents what it accomplished during the sprint • Typically takes the form of a demo of new features or underlying architecture • Informal • 2-hour prep time rule • No slides • Whole team participates • Invite the world Mountain Goat Software, LLC
    • Sprint retrospective • Periodically take a look at what is and is not working • Typically 15–30 minutes • Done after every sprint • Whole team participates • ScrumMaster • Product owner • Team • Possibly customers and others Mountain Goat Software, LLC
    • Start / Stop / Continue • Whole team gathers and discusses what they’d like to: Start doing Stop doing This is just one of many ways to do a sprint retrospective. Mountain Goat Software, LLC Continue doing
    • Game schedule cont’d 00:20 Presentation on Sprint Review & Sprint Retrospective 00:25 Sprint Review/Demo by each team (show the work) 00:30 Sprint Retrospective (what went well, what to improve) 00:32 Sprint Planning (decide how much to do) Mountain Goat Software, LLC
    • Game schedule cont’d 00:34 Day 1 in Sprint 2 (work) 00:38 Daily Scrum in Sprint 2 00:39 Day 2 in Sprint 2 (work) 00:43 Sprint Review/Demo by each team (show the work) 00:48 Sprint Retrospective 00:50 Wrap Up Mountain Goat Software, LLC
    • Where to go next • http://mountaingoatsoftware.com/scrum • http://scrumalliance.org • http://controlchaos.com Mountain Goat Software, LLC
    • A Scrum reading list • • • • • • • • • Agile and Iterative Development: A Manager’s Guide by Craig Larman Agile Estimating and Planning by Mike Cohn Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Software Development Ecosystems by Jim Highsmith Agile Software Development with Scrum by Ken Schwaber and Mike Beedle Scrum and The Enterprise by Ken Schwaber User Stories Applied for Agile Software Development by Mike Cohn Lots of weekly articles at www.scrumalliance.org Mountain Goat Software, LLC
    • Copyright notice • • • You are free: • • to Share―to copy, distribute and transmit the work to Remix―to adapt the work Under the following conditions • Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Nothing in this license impairs or restricts the author’s moral rights. • For more information see http://creativecommons.org/licenses/by/3.0/ • Credits: Mike Cohn, Mark Levison and Paul Heidema Mountain Goat Software, LLC
    • The Agile Manifesto invites wimpy-ness "… Individuals and interactions over processes & tools…" (Yayy!! I don't have to follow those stupid processes any more!) "… Working software over comprehensive documentation…" (W00t!! Dump the documentation! I LOVE this agile stuff!) "… Customer collaboration over contract negotiations…" (I'm done when I'm done and I never have to say when!) "… Responding to change over following a plan…" (No plans! No project managers! No architects! ) Mountain Goat Software, LLC Alistair Cockburn, 2010
    • Questions? Mountain Goat Software, LLC
    • Contacts linkedin.com/in/vivanov vladimir@ivanov.lv +371 29160633 v.ivanovs @vivanovs (Vladimir_ITSM) Mountain Goat Software, LLC