Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Tool Selection

10,386 views

Published on

Hope this help you select the right agile tooling.

Published in: Technology, Business
  • Interesting post. Your readers might also find real user reviews for many of these agile tools at IT Central Station to be helpful. As an example, this user writes in his review of CA Agile Central, "Vendors who were on our shortlist were JIRA (Atlassian) and AgileCraft. At the end of the day, we chose Agile Central, mainly for its robust capabilities and the ability to talk to other database systems." You can read the full review here: https://www.itcentralstation.com/product_reviews/ca-agile-central-review-40873-by-dennis-conte/tzd/c301-sbc-135.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • what is the difference between agile tool and QC tool ? How do they differ in analyzing the requirement
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • in my managerial this question was asked . I told in QC tool we have requirement coverage module--- is it correct or wrong?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • please reply
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • which tool do you use for requirements
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile Tool Selection

  1. 1. What tools do you use for Large Scale Agile?<br />
  2. 2. 2<br />Tool Need Identified<br />Background<br /><ul><li>Multiple Agile tracking tools used by early Agile teams
  3. 3. ISG transition to Agile beginning Sep 22nd, 2010</li></ul>Needs<br /><ul><li>Need to have an Agile management tool for new Agile teams to use
  4. 4. Need to be able to roll-up product status across ISG product lines</li></li></ul><li>Decision Space<br /><ul><li>The full ALM tool space is shown at left
  5. 5. This tool decision was focused on the highlighted areas
  6. 6. It is assumed that Documentation Management and Software Development will be handled externally to the tool</li></li></ul><li>Agile Tool Team Composition<br /><ul><li>Goals
  7. 7. Include at least one member from each team already doing Agile in ISG
  8. 8. Include at least one member from each Agile role (scrum master, product owner, developer, tester)
  9. 9. Keep team to a manageable a size
  10. 10. Team</li></li></ul><li>Decision Analysis Process<br />The team elected to use the Analytical Hierarchy Process (AHP) to conduct the decision analysis. This uses the following method to reach a decision.<br />Identify decision criteria <br />Identify alternatives<br />Do pairwise comparisons between the criteria in order to determine the relative weight of each<br />For each criteria, do pairwise comparisons of all alternatives to get the criteria score for each alternative<br />Summarize criteria contributions for each alternative<br />The alternative with the highest score is the recommendation<br />
  11. 11. Identification of Candidate Tools<br /><ul><li>Goals
  12. 12. Review all Agile tools currently in use within ISG
  13. 13. Review market leaders
  14. 14. Candidates
  15. 15. Quality Center (Hewlett-Packard)
  16. 16. Jira (Atlassian)
  17. 17. Team Foundation Server (Microsoft)
  18. 18. DevSuite (TechExcel)
  19. 19. Rally (Rally Software)
  20. 20. VersionOne (VersionOne Software)</li></ul>6<br />
  21. 21. Tool Needs<br />The team identified the five categories of needs shown below. Each category is further broken into individual criteria in the following pages.<br /><ul><li>Planning and Tracking
  22. 22. Story Definition
  23. 23. Development Integration
  24. 24. Quality Assurance
  25. 25. Infrastructure Operations</li></ul>7<br />
  26. 26. Planning and Tracking Criteria<br />The Planning & Tracking criteria focus on how scrum masters, product owners, and managers plan future work and track the current status of development. <br />Criteria<br /><ul><li>Agile Project Management
  27. 27. Agile Reports
  28. 28. Hierarchical Stories/Projects/Roll-Up
  29. 29. Multi-Team Program Management
  30. 30. Story, Task, and Kanban Boards</li></ul>*See notes section for details<br />8<br />Planning &<br />Tracking<br />Story <br />Definition<br />Development<br />Integration<br />Quality<br />Assurance<br />Infrastructure<br />Operations<br />
  31. 31. Story Definition Criteria<br />The Story Definition criteria focus on how product managers and owners enter the details of work to be completed for the coming iterations.<br />Criteria<br /><ul><li>Story Capture
  32. 32. Acceptance Criteria
  33. 33. Attachments
  34. 34. Tasks/Sub Tasks
  35. 35. UI Spec</li></ul>*See notes section for details<br />9<br />Planning &<br />Tracking<br />Story <br />Definition<br />Development<br />Integration<br />Quality<br />Assurance<br />Infrastructure<br />Operations<br />
  36. 36. Development Integration Criteria<br />The Development Integration criteria describe how well the candidate tool integrates with other tools commonly used for application development.<br />Criteria<br /><ul><li>IDE Integrations
  37. 37. Open API
  38. 38. Source Control
  39. 39. Integration Across Functional Subsystems</li></ul>*See notes section for details<br />10<br />Planning &<br />Tracking<br />Story <br />Definition<br />Development<br />Integration<br />Quality<br />Assurance<br />Infrastructure<br />Operations<br />
  40. 40. Quality Assurance Criteria<br />The Quality Assurance criteria detail how the testers manage defects and planned tests.<br />Criteria<br /><ul><li>Defect & Defect Suite Management
  41. 41. Automated Test Management
  42. 42. Integration with Quality Center
  43. 43. Manual Test Management</li></ul>*See notes section for details<br />11<br />Planning &<br />Tracking<br />Story <br />Definition<br />Development<br />Integration<br />Quality<br />Assurance<br />Infrastructure<br />Operations<br />
  44. 44. Infrastructure Operations Criteria<br />The Infrastructure Operations criteria focus on how the tool is brought in and maintained within the organization.<br />Criteria<br /><ul><li>Cost
  45. 45. Availability
  46. 46. Hosting Options
  47. 47. Configurations
  48. 48. Intangibles</li></ul>*See notes section for details<br />12<br />Planning &<br />Tracking<br />Story <br />Definition<br />Development<br />Integration<br />Quality<br />Assurance<br />Infrastructure<br />Operations<br />
  49. 49. Overall Category Weighting<br />13<br />
  50. 50. Criteria Weighting By Category<br />14<br />Infrastructure <br />Operations<br />Planning & Tracking<br />Quality Assurance<br />Development <br />Integration<br />Story Definition<br />
  51. 51. Candidate Tool Analysis<br />Quality Center<br /><ul><li>Pros
  52. 52. Already used widely within IVS
  53. 53. Very strong test and defect functionality
  54. 54. Cons
  55. 55. Very poor Agile UI (planning, stories, tasks, status)
  56. 56. Limited Agile functionality (boards, reports, resource planning)
  57. 57. Poor responsiveness</li></ul>Jira<br /><ul><li>Pros
  58. 58. Good implementation of common Agile items
  59. 59. Very strong development integration tools
  60. 60. Cons
  61. 61. Fair Agile UI (planning, stories, tasks, status)</li></ul>15<br />
  62. 62. Candidate Tool Analysis (cont)<br />Team Foundation Server<br /><ul><li>Pros
  63. 63. Across-the-board development integration
  64. 64. Acceptable implementation of common Agile items
  65. 65. Cons
  66. 66. Only integrated with Microsoft development tools
  67. 67. Did not provide good method for non-developers to access Agile information</li></ul>DevSuite<br /><ul><li>Pros
  68. 68. Across-the-board development integration
  69. 69. Used in other Deere factories
  70. 70. Cons
  71. 71. Very fragmented UI requires use of 4 separate tools to track Agile development
  72. 72. Somewhat limited Agile functionality (poor taskboards, prioritization, test plans)</li></ul>16<br />
  73. 73. Candidate Tool Analysis (cont)<br />17<br />Rally<br /><ul><li>Pros
  74. 74. Very strong Agile UI implementation
  75. 75. Included all targeted Agile functionality needs
  76. 76. Cons
  77. 77. Only fair support for development integration</li></ul>VersionOne<br /><ul><li>Pros
  78. 78. Strong Agile UI implementation
  79. 79. Included nearly all targeted Agile functionality needs
  80. 80. Cons
  81. 81. Less intuitive story hierarchy
  82. 82. Less functional test cases </li></li></ul><li>Final Scoring Results<br />18<br />
  83. 83. Final Score Contributions By Category<br />19<br />
  84. 84. Conclusions<br /><ul><li>As the team reviewed tools, it became apparent that the tools built to do Agile from the ground up provided better functionality and user interface than those tools that added Agile to existing functionality.
  85. 85. The team feels confident in the decision result that identifies Rally as the strongest candidate. Rally demonstrated strength in all targeted areas of Agile functionality and proved to be the quickest tool to both learn and use.</li></ul>20<br />
  86. 86. Chad “Agile Ninja” Holdorfwww.scaledagiledelivery.com<br />Hi, my name is Chad Holdorf and I call myself the Agile Ninja because I hate being called a Process Pro. The reason I hate the title Process Pro is because I love delivering products. In 2008 I was asked to lead a team in the development of a software project using Agile. My response was, “WHAT?!?!”  Today I’m proud to say I am all in on Agile | Lean Methodologies and teach it every day.<br />I work for a John Deere Intelligent Solutions Group in Des Moines, IA as an Scaled Agile Coach.  I’m not sure that is the right title, but my role is to roll out and support Agile at all locations.<br />The challenges I blog/tweet/talk about are related to how John Deere is tailed around hardware and waterfall processes. This drives me bonkers when we try to make are software follow a hardware process!<br />I’ve been applying Agile practices since Feb08. As an Agile Coach, I orchestrated the first large-scale Agile transformation within the company. This project included over 200 people and 30+ managers and was initiated, successfully, just four months prior to a critical product launch. I specializing in organizational change, optimization, efficiency and business value delivery, I make organizations better. Today 600+ people are practicing what I call “Scaled Agile Delivery Methodology” within John Deere.<br />It’s never been a better time to be a part of John Deere and we are going places in the world of software development! If you want to join Deere, you can see the job listings here.<br />

×