Downloaded 314 times
Uploaded byChad Holdorf
Agile Tool Selection
The document discusses the process used by an Agile team at John Deere's Intelligent Solutions Group to select an Agile management tool. The team used the Analytical Hierarchy Process to identify criteria, alternatives, weight criteria based on pairwise comparisons, score alternatives, and recommend Rally as the strongest candidate tool based on its strengths in planning, tracking, story definition, development integration, quality assurance and infrastructure operations.
More Related Content
Agile Tool Selection
- 1. What tools doyou use for Large Scale Agile?
- 2. 2Tool Need IdentifiedBackgroundMultipleAgile tracking tools used by early Agile teams
- 3. ISG transition toAgile beginning Sep 22nd, 2010NeedsNeed to have an Agile management tool for new Agile teams to use
- 4. Need to beable to roll-up product status across ISG product linesDecision SpaceThe full ALM tool space is shown at left
- 5. This tool decisionwas focused on the highlighted areas
- 6. It is assumedthat Documentation Management and Software Development will be handled externally to the toolAgile Tool Team CompositionGoals
- 7. Include at leastone member from each team already doing Agile in ISG
- 8. Include at leastone member from each Agile role (scrum master, product owner, developer, tester)
- 9. Keep team toa manageable a size
- 10. TeamDecision Analysis ProcessTheteam elected to use the Analytical Hierarchy Process (AHP) to conduct the decision analysis. This uses the following method to reach a decision.Identify decision criteria Identify alternativesDo pairwise comparisons between the criteria in order to determine the relative weight of eachFor each criteria, do pairwise comparisons of all alternatives to get the criteria score for each alternativeSummarize criteria contributions for each alternativeThe alternative with the highest score is the recommendation
- 11. Identification of CandidateToolsGoals
- 12. Review all Agiletools currently in use within ISG
- 13.
- 14.
- 15.
- 16.
- 17. Team Foundation Server(Microsoft)
- 18.
- 19.
- 20.
- 21. Tool NeedsThe teamidentified the five categories of needs shown below. Each category is further broken into individual criteria in the following pages.Planning and Tracking
Editor's Notes
- #9 Agile Project ManagementTracking release and sprint statusRelease planningAssigning tasks to resourcesLinking defects, stories, tasks, acc criteriaAgile ReportsAre the reports adaquate to get the information needed?Are the reports easy to read and generate?Can a SRS-style report be generated? If so, is it readable?Hierarchical Stories/Projects/Roll-UpCan multiple levels of stories be created?Can multiple levels of projects be created?Can reporting be done for any level of project in the roll-up?Can the tool display a tree structure that can be easily expanded and contracted?Multi-Team Program ManagementAbility to track multiple teams on the same project.Flexibility for moving folks from one team to another.Story, Task, and Kanban BoardsAbility to see a story board, a task board, and a kanban board.
- #10 Story CaptureSearch abilitiesRanking?rich textLink to test plan tied to this storyCustom fieldsTagsAdd a new branch?LongevityArchivingAcceptance Criteriacreate, edit, etc versioning?ownership?linking?pass/fail tracking?tie to automation?Attachmentsattachments internal?attachments linking to external files (hyperlink)?embedded photos/images?search attachments?change history/versioning?Tasks/Sub Taskscreate, edit, etchoursestimatedremainingtotaltie to storyassigned tostate trackingUI SpecAttachment only vs integrated Demand 1 - mock upDemand 2 - wireframe/low fidelity
- #11 IDE IntegrationsHow many IDE's does the tool integrate with, and what is the quality of the integration?Open APIDoes the tool provide a method to read and write data to it so that custom integrations can be written if needed?Source ControlWhat are the capabilities for tie/link to source code controlIntegration Across Functional SubsystemsIntegration between major componentsMajor components being:- issues/defects- source control- continuous integration (& automated test)- manual tests (& manual test management)- IDEEase of workflow between the tools
- #12 Defect & Defect Suite ManagementHow effectively are defects tracked in the system?Can they be tied to stories?Can they be tied to a Screen?Automated Test ManagementAutomation of testsDevelopment side of QAFunctional testsIntegration with Quality CenterCan the tool integrate with QC if we decide to continue to use it for defects and test plansManual Test ManagementCan test cases be created in the tool?Can they be tied to stories?Can the results of the test be recorded and tracked?
- #13 Cost Tool costHosting costLicense structure/countsAvailabilityUptime metrics acceptable?Hosting OptionsInternal and externalUpgradabilityConfigurationsUser access/setupTailor projects/custom fieldsAdmin optionsIntangiblesCoaches vs ToolsOverall look and feelLearning curveHelp