1 / 29

Agile Tools

Agile Tools. Supannika Koolmanojwong. Outline. Agile Iteration Planning Retrospective Analysis Risk Management. Agile Iteration Planning. Define categories of your project status for the next iteration To do, Doing, Done Goals, Tasks, WIP, Done.

carney
Download Presentation

Agile Tools

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 Tools Supannika Koolmanojwong

  2. Outline • Agile Iteration Planning • Retrospective Analysis • Risk Management

  3. Agile Iteration Planning • Define categories of your project status for the next iteration • To do, Doing, Done • Goals, Tasks, WIP, Done http://accurev.com/blog/2010/09/27/implementing-agile/

  4. Alternative Agile Boards http://theagileschool.blogspot.com/

  5. Big Picture http://www.planbox.com/blog/category/agile-project-management

  6. Burndown Chart http://www.infoq.com/articles/agile-kanban-boards

  7. Tricks http://www.xqa.com.ar/visualmanagement/

  8. Workshop 1 • 6 sticky notes per person • For this iteration (now to RDCR ARB) • Write • 2 “To-do” tasks • 2 “Doing” tasks • 2 “Done” tasks • Post on the board • Talk among team members • Add more, if needed Task Name 9 SK Your Abbreviation Hours Spent (for “Done”) Hours Estimated (for “to-do” and “Doing”)

  9. Retrospective Analysis • Think about the previous iteration • Smiley Face: What I liked... • Team coordination; progress of work • Sad Face: What I didn't like....   • Mr.X needs to step up; client has not given me Z • Light Bulb: What is now clear to me... • Finally, we have a full time !! • Cloud: What is still cloudy..... • When are we going to get the server ? http://theagileschool.blogspot.com/

  10. Agile Retrospective Board http://theagileschool.blogspot.com/

  11. Daily Retrospective Board • Niko-niko Calendar (or Smiley Calendar) • Puts a Smiley mark onto a calendar after the day's work, before leaving the team room. • member's mental health and motivation viewpoint http://drdobbs.com/architecture-and-design/201807863

  12. Workshop 2 • 4 sticky notes each, 2 notes for each category • Post them on the board • Smiley Face: What I liked... • Team coordination; progress of work • Sad Face: What I didn't like....   • Mr.X needs to step up; client has not given me Z • Light Bulb: What is now clear to me... • Finally, we have a full time !! • Cloud: What is still cloudy..... • When are we going to get the server ? • Talk among team members • Add as necessary SK

  13. Managing RisksTraditional vs Agile (1) http://www.solutionsiq.com/resources/agileiq-blog/bid/71750/Managing-Risk-in-Scrum-Part-2

  14. Managing RisksTraditional vs Agile (2) http://www.solutionsiq.com/resources/agileiq-blog/bid/71750/Managing-Risk-in-Scrum-Part-2

  15. Managing RisksTraditional vs Agile (3) http://www.solutionsiq.com/resources/agileiq-blog/bid/71750/Managing-Risk-in-Scrum-Part-2

  16. Five common risk areas [Tom DeMarco] • Intrinsic Schedule Flaw • In setting time and effort for budgets • Specification Breakdown • an agreement cannot be reached on what the requirements are • Scope Creep • increases the size of the project without a concomitant change in resources and time • Personnel Loss • creating a learning curve for the replacement persons • Productivity Variance • Underperformance or overperformance Ref: Tom DeMarco, Waltzing with Bears

  17. How does Agile address the risks? • Schedule Flaw • Estimating is a guess; Feedback loops to mitigate invalid guesses; • Update the release plan at the end of every sprint • Prioritizing the product backlog to deliver value sooner (based on value, not time) by looking for early release opportunities (Value + time) http://www.solutionsiq.com/resources/agileiq-blog/bid/70560/Managing-Risk-in-Scrum-Part-1

  18. 2. Specification Breakdown • Having a dedicatedproduct owner to communicate the customer needs and decisions about what the product should do • Ensure alignment between what is requested and how it can be delivered http://www.solutionsiq.com/resources/agileiq-blog/bid/70560/Managing-Risk-in-Scrum-Part-1

  19. 3. Scope Creep • every scrum ceremony, may discover new things to include • New requirement, new backlog items • Product owner will evaluate the new product backlog items • Add • Delete • Trade-out in priority with other items http://www.solutionsiq.com/resources/agileiq-blog/bid/70560/Managing-Risk-in-Scrum-Part-1

  20. 4. Personnel Loss • With self-organizing teams, members focusing on work and problems to solve, thus resulting in higher morale • Daily Stand-up meetings, shared knowledge http://www.solutionsiq.com/resources/agileiq-blog/bid/70560/Managing-Risk-in-Scrum-Part-1

  21. 5. Productivity Variance • Teams guess on how much work they can do in their first iteration • Evaluate performance at Sprint review • Burndown chart • Velocity • Mitigating or correcting the difference variation happens in the next sprint http://www.solutionsiq.com/resources/agileiq-blog/bid/70560/Managing-Risk-in-Scrum-Part-1

  22. Agile risk management activities

  23. Sample Agile Project Risks http://www.newproductdynamics.com/Publications/SoftwareDevel0405.pdf

  24. Agile Risk Management Tools

  25. Agile Risk Management Tools

  26. Risk Strategies • Risk Avoidance • COTS product C is almost as good as B, and it can talk to A • Delivering on time is worth more to the customer than the small performance loss • Risk Transfers • If the customer insists on using A and B, have them establish a risk reserve. • To be used to the extent that A and B can’t talk to each other • Risk Reduction • If we build the wrappers and the CORBA corrections right now, we add cost but minimize the schedule delay • Risk Acceptance • If we can solve the A and B interoperability problem, we’ll have a big competitive edge on the future procurements • Let’s do this on our own money, and patent the solution

  27. Risk Radar Tool Business Technical Need all VPs meeting Sync interface of M1 – M5 Coordination Execution Challenge in training Sales Rep Migrate data from S2 http://www.bigvisible.com/tag/agile-project-management/

  28. Risk Radar Tool Business Technical Next Four Sprints Need all VPs meeting Sync interface of M1 – M5 Next Two Sprints Coordination Execution Challenge in training Sales Rep Migrate data from S2 http://www.bigvisible.com/tag/agile-project-management/

  29. Workshop 3 • As a team, brainstorm the risk items • Team 5 – using Risk Exposure • Team 11, 12 - use tool#2 • Obstacles, Mitigating, Containing, Accepting, Avoiding • Team 13,14 – use Risk Radar Tool • Business /Technical • Coordination/Execution • Before ARB/ Before CCD

More Related