1 / 29

Agile In Practice

Explore the practical application of Agile methodologies in software development, including SCRUM workflows, roles, and artifacts. Learn about Agile challenges and how to adapt processes for success.

jonass
Download Presentation

Agile In Practice

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile In Practice • Benjamin Booth • Fall 2009

  2. Proprietary Programmer/Architect 2 5

  3. Proprietary Author/Bloggerbenjaminbooth.com 3

  4. Prescriptive-style History • Restrict change to improve predictions • Drive with the plan • Communicate with documents • Interchangeable programmers 4

  5. Waterfall Is Expensive!

  6. Waterfall Not all Bad • Space shuttle flight control system • Requirements are well defined • Unlimited resources • Useful for < 5% of all software projects 6

  7. Typical Requirements • The site shall have a ‘nice looking’ menu page for an existing restaurant’s seven year old website. (Nice looking is defined by the customer.) • The system shall have the ability to edit the menu online. Current menus are stored in a MS Word document. • The site shall have a ‘Suggestion’ capability. Users can use a form to submit suggestions which get stored and also emailed to the owner. 7

  8. Agile • People (users) are the focus • Measure success with working software • Expect and embrace change • Use small, skilled, motivated teams agilemanifesto.org 8

  9. Agile - SCRUM Style • Japanese origin • Whole team • 1995 OOPSLA, by Jeff Sutherland and Ken Schwaber • Skeleton of practices and roles 9

  10. Proprietary SCRUM Workflow 10

  11. SCRUM Roles • Product Owner: Manages the backlog • Scrum Master: Coach the process • Team Member: Write code 11

  12. Practice Tip • Create User Advocates • Include User Advocates in: • Story creation • Priority setting • Interaction design sessions

  13. SCRUM Artifacts • Backlog • Sprint Burn Down • Sprint Backlog • Past Backlogs 13

  14. Practice Tip • Store Backlogs electronically • Use physical Task Boards

  15. Proprietary • Backlog • Sprint Backlog • Taskboard • Sprint Burn Down Artifacts 15

  16. Proprietary • Backlog • Sprint Backlog • Taskboard • Sprint Burn Down Artifacts 16

  17. Proprietary • Backlog • Sprint Backlog • Taskboard • Sprint Burn Down Artifacts 17

  18. Proprietary • Backlog • Sprint Backlog • Taskboard • Sprint Burn Down Artifacts 18

  19. Practice Tip • Keep old Sprint Backlogs & Burndowns • Keep old tasks • Use for velocity calculations • Helps identify trends 20

  20. Each developer has a set of cards with Fibonacci series numbers (2,3,5,8,13,etc..) A user story is presented Each developer picks the card representing the number of story points the user story should take Everyone then shows their cards Discussion happens until agreement on a number Repeat for each user story Schedule a sprint with the required number of story points based on your team’s velocity Planning Poker 21

  21. As a patron, I want to... • easily navigate to the menu from the home page so that I can make a phone order (delivery) • be able to make suggestions for improvements to my overall dining experience 22

  22. As the restaurant manager, I want to... • create, update and delete menu items so that it stays interesting and keeps people coming back • generate a PDF of the menu so that I can give it to the printer for creating ‘real’ menus • get customer feedback emailed to me so I can quickly respond to problems and also pass on compliments to the staff 23

  23. Agile Challenges • Access to real customers • Large, distributed teams • Industry misperceptions • Command-and-control culture 24

  24. Summary • Waterfall or nothing still predominant • Agile is highly adaptive, people centric • SCRUM is an effective Agile process skeleton • If your process isn’t working adapt it 25

  25. Practice Tip • Introduce internally • Strategy and architecture a must • Strategy drives estimates 26

  26. Practice Tip • Allocate QA time explicitly • Keep PM simple but do it • Keep improving your process 27

  27. Q&A

  28. References • http://en.wikipedia.org/wiki/Agile_software_development • http://www.waterfall2006.com/ • http://www.agileManifesto.org/ • http://www.codinghorror.com/blog/archives/000588.html • http://www.drdobbsonline.net/architect/207100381 • http://en.wikipedia.org/wiki/Scrum_%28management%29 • http://spectrum.ieee.org/sep05/1685/failt1 As a patron, I want to 29

  29. As a patron, I want to easily navigate to the menu from the home page so that I can make a phone order (delivery) As a patron, I want to be able to make suggestions for improvements to my overall dining experience As the restaurant manager, I want to create, update and delete menu items so that it stays interesting and keeps people coming back As the restaurant manager, I want to generate a PDF of the menu so that I can give it to the printer for creating ‘real’ menus As the restaurant manager, I want to get customer feedback emailed to me so I can quickly respond to problems and also pass on compliments to the staff

More Related