Agile intro module 1

Agile Introductie Module 1 - Algemene introductie 1

Agile volgens Dilbert 2

Sprint Backlog TO-DO IN WORK DONE Wat is Agile? Scrum en XP Toepassing & risico’s 3

User Story Als een cursist Wil ik de achtergronden van Agile snappen Om Agile in diverse situaties goed toe te kunnen passen 5

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. 6

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 customer's 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. 7

Agile - tegenbeweging • Tegen: • waterval ontwikkeling • micro management • minachting vakmanschap ontwikkelaars 8

Principes geen Regels • YAGNI - you ain’t gonna need it • BDUF - big design up front • BPUF - big planning up front • Simplicity - the art of maximizing the amount of work NOT done • Fail fast 9

Andere planning principes Scope FIXED ESTIMATE Traditioneel Time Cost 10

Andere planning principes Scope Time Cost FIXED Agile ESTIMATE Traditioneel Time Cost Scope 10

User Story Als een cursist Wil ik weten wat Scrum is en XP Omdat ik daar misschien wel mee wil gaan werken 14

Scrum • PROJECT MANAGEMENT aanpak • Dus zelfde doel als Prince2 • Maar, een heel andere aanpak! 15

The big picture Image available at www.mountaingoatsoftware.com/scrum

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. 17

Scrum framework Roles • Product owner • ScrumMaster Ceremonies • Team • Release planning • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts • Deﬁnition of Done 18

Product owner • Deﬁne the features of the product • Decide on release date and content • Be responsible for the proﬁtability 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) • Teams are self-organizing • Ideally, no titles but rarely a possibility • Membership should change only between sprints Mountain Goat Software, LLC

Release Planning Product Vision 1 2 3 4 5 6 7 8 User User User User Story Story Story Story Epic User User User User Epic Story Story Story Story Epic Epic User User User User User Story Story Story Story Story User User User User User User Story Story Story Story Story Story 24

Release Planning Product Vision 1 2 3 4 5 6 7 8 User User User User Story Story Story User stories are the Story Epic Agile way of documenting User User User User Story Story Story requirements. Epic Story As a <user role> Epic Epic User User User User User Story Story Story I want <something> Story Story So I can achieve <value> User User User User User User Story Story Story Story Story Story 24

Sprint planning meeting Team capacity Product backlog Business conditions Current product Technology 25

Sprint planning meeting Team capacity Sprint prioritization Product • Analyze and evaluate product backlog backlog • Select sprint goal Business conditions Current product Technology 25

Sprint planning meeting Team capacity Sprint prioritization Product • Analyze and evaluate product Sprint backlog backlog goal • Select sprint goal Business conditions Current product Technology 25

Sprint planning meeting Team capacity Sprint prioritization Product • Analyze and evaluate product Sprint backlog backlog goal • Select sprint goal Business conditions Sprint planning • Decide how to achieve sprint Current goal (design) product • Create sprint backlog (tasks) from product backlog items (user stories / features) Technology • Estimate sprint backlog in hours 25

Sprint planning meeting Team capacity Sprint prioritization Product • Analyze and evaluate product Sprint backlog backlog goal • Select sprint goal Business conditions Sprint planning • Decide how to achieve sprint goal (design) Current Sprint product • Create sprint backlog (tasks) from product backlog items (user backlog stories / features) Technology • Estimate sprint backlog in hours 25

Sprint planning • Team selects items from the product backlog they can commit to completing • Sprint backlog is created • Tasks are identiﬁed and each is estimated (1-16 hours) • Collaboratively, not done alone by the ScrumMaster • High-level design is considered As a vacation Code the middle tier (8 hours) planner, I want to Code the user interface (4) Write test ﬁxtures (4) see photos of the Code the foo class (6) hotels. Update performance tests (4) 26

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 27

Everyone answers 3 questions 1 What did you do yesterday? 2 What will you do today? 3 Is anything in your way? • These are not status for the ScrumMaster • They are commitments in front of peers 28

The sprint review • Team presents what it accomplished during the sprint • Typically or underlying architecture of new features takes the form of a demo • Informal • 2-hour prep time rule • No slides • Whole team participates • Invite the world 29

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 30

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 Continue doing do a sprint retrospective. 31

Scrum framework Roles • Product owner • ScrumMaster • Team Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts • Deﬁnition of Done 32

Product backlog •The requirements •A list of all desired work on the project •Ideally expressed the users each item has value to such that or customers of the product • Prioritized by the product owner This is the • Reprioritized at the start of each sprint product backlog 33

A sample product backlog Backlog item Estimate Allow a guest to make a reservation 3 As a guest, I want to cancel a reservation. 5 As a guest, I want to change the dates of a 3 reservation. As a hotel employee, I can run RevPAR reports 8 (revenue-per-available-room) Improve exception handling 8 ... 30 Or use T-Shirt ... sizes (S/M/L) 50 34

The sprint goal • A short statement of what the work will be focused on during the sprint Life Sciences Support features necessary for Database Application population genetics studies. Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicators than company ABC with real-time, streaming data. 35

Managing the sprint backlog • Individuals sign up for work of their own choosing • Work is never assigned • Estimated work remaining is updated daily • Any team member can add, delete or change the sprint backlog • Work for the sprint emerges • If work is unclear, deﬁne a sprint backlog item with a larger amount of time and break it down later • Update work remaining as more becomes known 36

Deﬁnition of Done • Wanneer is een taak (een stuk code) af? 37

Deﬁnition of Done Uit een presentatie van Ken Schwaber: 1. I can readily understand the software and where and how things happen; 2. When I change or add to part of the software, there are no unintended or poorly designed dependencies; 3. I can read the code without lookin for tricks or poorly deﬁned and • labeled variables or is een taak (een stuk code) af? Wanneer data; 4. I don’t need the person(s) who wrote the code to explain it to me; 5. There are a full set of (automated) tests to check that the function works as expected; 6. When I change something and add to the test, I can check that the entire change and product continuous to work; 7. How thing work and hang together is transparent, and 8. Standard, well-known design principles have been adhered to. 37

Responsibilities Team PO Scrum Master

XP - eXtreme Programming • ONTWIKKEL aanpak 39

XP Practices 40

User Story Als een cursist Wil ik even brainstormen over kansen en risico’s van Agile Omdat ik nu een docent in de buurt heb die vragen kan beantwoorden Omdat dat de ‘slideware’ laat bezinken Omdat ik die vragen bij toepassing in ons bedrijf ook ga tegenkomen 44

Retrospective • Workshop • 3 groepjes, 2x10 minuten • “Waar ben ik helemaal enthousiast over, wat ga ik morgen al toepassen” • “Dit gaat bij ons nooit werken, want ...” 45

Ere wie ere toekomt • Diverse slides zijn overgenomen uit Redistributable Scrum Introduction - Scrum Alliance 48

Agile intro module 1

by André Heijstek on Nov 05, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 68

Statistics

Agile intro module 1 — Presentation Transcript