Agile intro module 4


Published on

Published in: Business
  • 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
  • \n
  • \n
  • \n
  • Toepassing op planning:\n1\n- ga bij elkaar zitten tijdens release/sprint planning\n- leg uit wat je bedoelt met een requirement\n2\n- voor een sprint van 3 weken kan je veel details wel onthouden, documenteer alleen het noodzakelijke\n- snelle oplevering zorgt ook voor snelle leercurve voor schatten en plannen\n3\n- ga bij elkaar zitten ...\n4\n- elke nieuwe sprint kan iets volledig anders zijn dan vooraf gedacht\n
  • Toepassing op Schatten en Plannen\n1. Korte sprints, snelle feedback\n2. Planning meeting - creeer gevoel van “abundance”\n3. Technical debt\n4. Prioritiseren - belangrijke zaken in vroege sprints\n5. Team - self-org\n6. Sprint review / retrospective, velocity\n7. Continue feedback, daily-scrum, sprint review\n8. Release planning / sprint planning\n9. Sprint\n10. Daily scrum / sprint planning\n11. Self-org\n12. Sprint plan, release plan, daily scrum, sprint review\n
  • Agile intro module 4

    1. 1. Agile Intro Module 4Invoering van Agile/Scrum 1
    2. 2. Agenda Overzicht planning & estimating Case Release Plan Iteration Plan2
    3. 3. Agenda Overzicht planning & estimating Case Release Plan Iteration Plan3
    4. 4. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.4
    5. 5. 12 principes Our highest priority is to satisfy the customer Working software is the primary 1 measure of progress. 7 through early and continuous delivery of valuable software. Agile processes promote sustainable Welcome changing requirements, even late in development. The sponsors, developers, 2 and users should be able to maintain a 8 development. Agile processes harness change for the customers competitive advantage. constant pace indefinitely. Continuous attention to technical Deliver working software frequently, from a 3 excellence and good design enhances 9 couple of weeks to a couple of months, with a agility. preference to the shorter timescale. Simplicity--the art of maximizing the Business people and developers must work 4 amount of work not done--is essential. 10 together daily throughout the project. The best architectures, requirements, Build projects around motivated individuals. 5 and designs emerge from self-organizing teams. 11 Give them the environment and support they need, and trust them to get the job done. At regular intervals, the team reflects The most efficient and effective method of on how to become more effective, then 6 tunes and adjusts its behavior 12 conveying information to and within a development team is face-to-face conversation. accordingly.5
    1. A particular slide catching your eye?

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