Leonidas Oy - Agile Project Management @Demola 2010-06-09


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Worked agile methods since 2006 technical lead project manager agile trainer and coach
  • Worked with Scrum since 2007 team member technical lead certified scrum master
  • SOFTWARE COMPANY SPECIALIZING IN RAPID PRODUCT DEVELOPMENT AND AGILE METHODS. rapid prototyping, 7 day project agile coaching and training software development. located in Tampere city centre  
  • STUDIES: work part-time with the projectYOUNG TEAMS: full of energy, enthusiastic, team roles and working habits still developingCUSTOMER: communication and how to get the most out of every contactSCHEDULE: part-time, creating abstract piece of workDiscuss if these are correct, take notes if comments are given
  • Any questions so far?
  • How many have heard of Scrum?How many have used?
  • There’s no better day to hold a agile development course than today. The manifesto meeting was held exactly 9 years ago, on Feb 11-13 2001Working software is the primary measure of progress. Building the project on trust, instead of contracts, is more efficient and builds a better relationship between the vendor and the customer.The 12 agile principles describe in more detail what agile is all about.
  • Ok, so now we know the basics. Agile is the general term for many things that lay underneath it. (Käy läpi nämä sisällöt.) What belongs to agile? If something corresponds to agile values, then it is agile. - Lean for example is a set of principles and ways of organizing a project, that is interrelated to agile. - Scrum is a specific technique for organizing a project, and we will learn a bit more about it today. Scrum is one of the agile practices and has been derived from lean principles.Next, let’s take a few examples on agile companies.
  • How many have heard of Scrum?How many have used?
  • - Process from product backlog to production quality software- iterative and time-boxed
  • - Process from product backlog to production quality software- iterative and time-boxed
  • - Process from product backlog to production quality software- iterative and time-boxed
  • -Go thru shortly
  • FEEDBACK:COMMITMENT: TEAM WORK: TIME: in order to use Scrum, allocate at least 10 h/week for your project. One month is even better, you get two solid sprints.
  • How many have heard of Scrum?How many have used?
  • Start shop, 5 days for development, demo shop1-2 devs, (graphic designer), Product Owner, sales guy, demo material creatorRetrospectives, code templates, communication
  • PLACE: Open space office, ad hoc meetings, 45-15 ruleTOOL: requirements backlog, shared spreadsheet
  • SW is deployed continuously and source code provided, tech risks solved in the beginningData model and next development steps provided, appr. 1-2 h of work
  • Breaks the iron triangle (fixed scope, resources, schedule) of software development.Rather than talking about contract details, we start a discussion with our customer about the goal of the project, users who are going to use the system, what are the most essential features and functionality, etc
  • Backlog: prioritization and estimationWe evaluate what’s important and what’s not. Estimations show us what can be delivered in the given time.
  • How many have heard of Scrum?How many have used?
  • How many have heard of Scrum?How many have used?
  • Build the Tallest Freestanding Structure: The winning team is the one that has the tallest structure measured from the table top surface to the top of the marshmallow. That means the structure cannot be suspended from a higher structure, like a chair, ceiling or chandelier.The Entire Marshmallow Must be on Top: The entire marshmallow needs to be on the top of the structure. Cutting or eating part of the marshmallow disqualifies the team.  Use as Much or as Little of the Kit: The team can use as many or as few of the 20 spaghetti sticks, as much or as little of the string or tape. The team cannot use the paper bag as part of their structure.Break up the Spaghetti, String or Tape: Teams are free to break the spaghetti, cut up the tape and string to create new structures.The Challenge Lasts 18 minutes: Teams cannot hold on to the structure when the time runs out. Those touching or supporting the structure at the end of the exercise will be disqualified. 
  • Leonidas Oy - Agile Project Management @Demola 2010-06-09

    1. 1. Agile Project ManagementCourse And Workshop<br />Demola, June 9, 2010<br />
    2. 2. Setup<br />Please set your mobile to silent mode<br />Contribute – ask and share your experience<br />Give feedback – remember to fill the form<br />
    3. 3. Introductions<br />
    4. 4. Project Manager, Agile Coach, CSM<br />Jarno Keskikangas<br />
    5. 5. Senior Software Engineer, Certified Scrum Master<br />Harri Lammi<br />
    6. 6. Software specialist, Agile coach<br />Antti Tarvainen<br />
    7. 7. Agile Software Development<br />Leonidaswww.leonidasoy.fi<br />
    8. 8. INTRODUCE YOURSELF<br />Project managers<br />Developers / designers<br />Other?<br />Thanks for answering our questionnaire!<br />
    9. 9. DEMOla: FACTS oR FICTION?<br />Demola project is done in addition to studies<br />Young and eager teams<br />Customer with limited time and availability<br />Project schedule difficult to estimate<br />The greatest obstacle preventing you to deliver as awesome results as possible is ______________ ?<br />TODAY’S GOAL: Helping you to be more productive by using agile methods<br />
    10. 10. OUR THEMES TODAY<br />Agile development in prototyping and small projects<br />Workshop: Using agile methods in your project<br />
    11. 11. schedule<br />1 h: Introductions andagile development<br />Break<br />1 h: Workshop and exercises<br />
    12. 12. Introducing agile<br />
    13. 13. What is agile?<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation <br />Customer collaboration over contract negotiation <br />Responding to change over following a plan<br />… That is, while there is value in the items on the right, we value the items on the left more.<br />http://agilemanifesto.org/<br />
    14. 14. Agile umbrella<br />
    15. 15. A Brief Look At Scrum<br />
    16. 16. What is scrum<br />Iterative incremental framework for managing complex work<br />
    17. 17. What is scrum<br /> Scrum is based on the belief that best results are achieved via:<br />Cross-functional team<br />Iterative and time-boxed development<br />
    18. 18. Scrum in one picture<br />
    19. 19. Scrum framework<br />Roles: <br />Product Owner<br />Team<br />Scrum Master<br />Events: <br />Sprint Planning<br />Sprint Review<br />Sprint Retrospective<br />Daily Scrum<br />Artifacts:<br />Product Backlog<br />Sprint Backlog<br />Burndown Charts<br />
    20. 20. Scrum requires…<br />Commitment<br />Communication<br />Colocation<br />Team<br />
    21. 21. CASE STUDY:Agile Principles in Rapid Prototyping<br />
    22. 22. Five solutions to boost team’s performance in rapid prototyping<br />
    23. 23. Rapid prototyping<br />ProtoSonni<br />From scratch to delivery in seven days<br />Fixed price, fixed schedule<br />Cross-functional team of 4-6 persons<br />Ongoing process improvement<br />
    24. 24. PROTOTYPING VS. LONG PROJECTS<br />Scrum is too heavy for prototyping, but fits better for longer projects (> 1 month)<br />You can still be agile by using agile principles<br />
    25. 25. agile in rapid prototyping<br />Booster #1: Team works in the same place!<br />Booster #2: One simple management tool<br />=> Individuals and interactions over processes and tools<br />
    26. 26. agile in rapid prototyping<br />Booster #3: Deploy early and often<br />=> Working software over comprehensive documentation<br />
    27. 27. agile in rapid prototyping<br />Booster #4: Packaged service<br />Fixed price, fixed schedule, open scope<br />Start shop and design draft set the direction<br />=> Customer collaboration over contract negotiation<br />
    28. 28. agile in rapid prototyping<br />Booster #5: Evaluate backlog continuously<br />=> Responding to change over following a plan<br />
    29. 29. ?<br />Questions?<br />
    30. 30. EXERCISE:Touch the ball<br />
    31. 31. Let’s take a break!<br />
    32. 32. Workshop Outline<br />Setting the stage<br />Open discussion on implementing agile methods in Demola<br />Group work and coaching<br />Teams gather to work on 1-2 development problems decided in the open discussion <br />Wrap up<br />Teams present their solutions<br />
    33. 33. TIME’S UP!<br />
    34. 34. EXERCISE:The Marshmallow Challenge<br />
    35. 35. The Marshmallow Challenge<br />Build the tallest Freestanding structure<br />The Entiremarshmallow must be on top<br />Use as much or as little of the kit<br />Break up the spaghetti, string or tape<br />The challenge lasts 3 x 6 minutes<br />
    36. 36. Further reading and resources<br />Books<br />Ken Schwaber: Agile Project Management with Scrum<br />Mary and Tom Poppendieck: Lean Software Development: An Agile Toolkit<br />Esther Derby, Diana Larsen: Agile Retrospectives: Making Good Teams Great<br />On the web<br />http://agilemanifesto.org/ -> The 12 Agile Principles<br />http://www.agilealliance.org/<br />http://www.scrumalliance.org/<br />http://leonidasoy.fi/blog -> How To Deliver Software In 7 Days<br />
    37. 37. Thank you!<br />Jarno.keskikangas@leonidasoy.fi<br />