CSC/ECE 517 Fall 2012/ch2a 2w7 ma: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
 
(112 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<p>Scrum Tools - This page gives survey of the tools that can be used for practicing scrum. While writing the survey, it considers the features offered by each of them, the scenarios in which each of them can be used considering what features it has and what features it lacks, cost involved etc. Give suitable examples wherever necessary.</p>
<p>Scrum Tools - This page gives survey of the tools that can be used for practicing scrum. It considers the features offered by each of them, the scenarios in which each of them can be used considering what features it has and what features it lacks, cost involved etc.</p>


== Overview ==
== Overview <ref name = "Scrum" />==


===Scrum===
===Scrum===
Scrum is an iterative and incremental agile software development method for managing software projects
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] is an [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental agile software development]<ref name = "iterative" /> method for managing software projects and products or application development. Scrum focuses on project management institutions where it is difficult to plan ahead. Mechanisms of [http://en.wikipedia.org/wiki/Empirical_process_(process_control_model) empirical process control], where feedback loops that constitute the core management technique are used as opposed to traditional command-and-control oriented management. It represents a radically new approach for planning and managing projects, bringing decision-making authority to the level of operation properties and certainties.
and product or application development.Scrum focuses on project management institutions where it is
difficult to plan ahead. Mechanisms of empirical process control, where feedback loops that constitute the
core management technique are used as opposed to traditional command-and-control oriented
management.[citation needed] It represents a radically new approach for planning and managing projects,
bringing decision-making authority to the level of operation properties and certainties.
<ref name = "Scrum" />


===Scrum Tools===
===Scrum Tools===
Scrum can be implemented through a wide range of tools. Many companies use universal tools, such as
Scrum can be implemented through a wide range of tools. Many companies use universal tools, such as spreadsheets to build and maintain artifacts such as the [http://www.daily-scrum.com/scrum/sprint/backlog sprint backlog]. There are also [http://en.wikipedia.org/wiki/Open_source open-source] and [http://en.wikipedia.org/wiki/Proprietary proprietary] packages dedicated to management of products under the Scrum process. Other organizations implement Scrum without the use of any tools and maintain their [http://en.wikipedia.org/wiki/Artifact artifacts] in hard-copy forms such as paper, whiteboards and sticky notes.
spreadsheets to build and maintain artifacts such as the sprint backlog. There are also open-source and
proprietary packages dedicated to management of products under the Scrum process. Other organizations
implement Scrum without the use of any tools, and maintain their artifacts in hard-copy forms such as
paper, whiteboards, and sticky notes
<ref name = "Scrum" />


== Selecting The Right Tool <ref name = Selecting_the_tool/>==


Here are some of the factors which should be considered before selecting the correct scrum tool -


== Selecting the right tool <ref name = Selecting_the_tool/>==  
=== Primary Factors ===


The Four Primary Factors
* Does the tool improve visibility?
- Scrum requires transparency to succeed. Everyone who needs to know about the project from the developers to the [http://en.wikipedia.org/wiki/Stakeholder stakeholders] and maybe even the customer should be able to use the tool. There is no point using a tool if only a [http://www.mountaingoatsoftware.com/scrum/scrummaster Scrum Master] or a few people can use it and everyone else has to rely on email.


* Improved visibility -  
* Does the tool improve communication?
- Tools can be used to open up channels of communication. For example, allowing a developer to comment on a [http://en.wikipedia.org/wiki/User_story user story] and have a remote customer reply back – setting up direct communication between developer and customer and bypassing all the bureaucracy in the middle.


Agile requires transparency to succeed. Can everyone who needs to know about the project from the developers to the stakeholders and maybe even the customer be able to use the tool? There is no point using a tool if only a ScrumMaster or a few people can use it and everyone else has to rely on email.
* Does the tool reinforce trust?
- Example: A team member forgot to update the estimate for Friday. He remembers on Monday. Can you set the estimate for Friday on Monday? In a “high trust” tool like pen & paper: you can just pick up a pen and redraw the [http://msdn.microsoft.com/en-us/library/ff731588.aspx burndown]. In a “low trust” tool, you cannot do this because it is considered as meddling with the past recorded history of actions.


Does the tool improve communication?
* Does the tool adapt to the way you work?  
- Each team is going to use the tool differently. Some tools adapt to the way you work, other tools force you to work the way the tool is setup. Because of the self-managed nature of scrum, it is important that the tool support the team, and the team should not have to change their working to fit the tool.


For example: Do team members start “reporting” status to the scrummaster so that the tool can be updated with their status. This is a common dysfunction that can occur with a tool and can reduce communication – ultimately leading to project failure.
=== Secondary Factors ===


Tools can be used to open up channels of communication. For example, allowing a developer to comment on a user story and have a remote customer reply back – setting up direct communication between developer and customer and bypassing all the bureaucracy in the middle.
* Standalone, monolithic or integrated :


Does the tool reinforce trust?
- Standalone tools let you create users, stories, iterations and tasks and generate some reports like [http://msdn.microsoft.com/en-us/library/ff731588.aspx burndown] or velocity. Basic, but useful when you want something simple.


Example: A team member forgot to update the estimate for friday. He remembers on monday. Can you set the estimate for friday on monday?
- Integrated tools do only project management, but they can integrate with external tools like other bug tracking tools, source control, wikis and so on. For example, you will be able to synchronize bugs from the bug tracker to the PM tool or link tasks in the tool with code commits and so on. They can provide an overview across multiple tools in use.


In a “high trust” tool like pen & paper: you can just pick up a pen and redraw the burndown. In a “low trust” tool, you cannot do this because it is considered as meddling with the past recorded history of actions.
- Monolithic tools support the entire life-cycle like document management, bug tracking, artifact management over and above standard PM functionality all within a single tool. Advantages of monolithic are that all components are tightly integrated. Disadvantage is that you have to discard all your existing tools to move to a monolithic one. Also if the monolithic tool does not support a particular component (like continuous integration or code analysis) you may still have to use multiple tools.


Does the tool adapt to the way you work?
* Usability :


Each team is going to use the tool differently. Some tools adapt to the way you work, other tools force you to work the way the tool is setup. Because of the self-managed nature of agile, it is important that the tool support the team, and the team should not have to change their working to fit the tool.
- How usable is the tool? When you have poor usability, people may resent working with the tool and might start working around the tool instead. Tools with poor usability may also call for additional unplanned expenditure in training and support. You also have issues of general resentment by the team at whoever foisted the tool upon them.


For example, a tool may enforce a particular workflow, which may not be the way the team works.
* Pricing model :


Secondary Factors
- Is the tool open source, free or commercial? For commercial tools, it the pricing per-user or per-project? Subscription or one-time payment? What is your risk exposure should the team size or number of projects increase? What is the total cost of ownership, including training, support, customizations etc. How does it fit your budget?


Standalone, monolithic or integrated?
==Low Tech Scrum Tools<ref name = simple_scrum_tools/>==
*Index cards :
- The [http://en.wikipedia.org/wiki/Extreme_programming eXtreme Programming (XP)] community swears by the use of standard index cards for a wide variety of modeling techniques, and in particular [http://en.wikipedia.org/wiki/Class-responsibility-collaboration_card Class Responsibility Collaborator (CRC]) modeling.


Standalone tools do only agile project management. You can create users, stories, iterations and tasks and generate some reports like burndown or velocity. Basic, but useful when you want something simple.
*Post-It notes :
- Post-It notes are also an option, for example one can develop an abstract/essential [http://en.wikipedia.org/wiki/User_interface user interface] prototype using Post-Its on large sheets of paper. This is part of a technique called essential user interface modeling.


Integrated tools do only project management, but they can integrate with external tools, like other bug tracking tools, source control, wikis and so on. For example, you will be able to synchronize bugs from the bug tracker to the PM tool, or link tasks in the tool with code commits and so on. They can provide an overview across multiple tools in use.
*Paper :
- Pieces of paper, or index cards, tacked onto a whiteboard and connected by strings can be used for a wide variety of models. For example the individual sheets of paper can represent database tables and the lines relationships between tables on a physical data model, or the sheets can represent screens and the strings navigation flows between screens on a user interface flow diagram, or the sheets can represent use cases and actors and the strings represent associations between them on a [http://www.andrew.cmu.edu/course/90-754/umlucdfaq.html UML use case diagram].  


Monolithic tools support the entire lifecycle like document management, bug tracking, artifact management over and above standard PM functionality all within a single tool.
*Plain old whiteboards (POWs) :
- A whiteboard for sketching on is likely the most common modeling tool in use.  A digital camera can easily make copies of sketches that one wants to keep.


Advantages of monolithic are that all components are tightly integrated. Disadvantage is that you have to discard all your existing tools to move to a monolithic one. Also if the monolithic tool does not support a particular component (like continuous integration or code analysis) you may still have to use multiple tools.
==Examples of Open Source Scrum Tools<ref name = "Examples_of_open_source_scrum_tools" />==
Here are some of the examples of open-source scrum project management tools -


Usability
===Agilefant<ref name = agilefant/>===
 
How usable is the tool? When you have poor usability, people may resent working with the tool and might start working around the tool instead. Tools with poor usability may also call for additional unplanned expenditure in training and support. You also have issues of general resentment by the team at whoever foisted the tool upon them.
 
Pricing model
 
Is the tool open source, free or commercial? For commercial tools, it the pricing per-user or per-project? Subscription or one-time payment? What is your risk exposure should the team size or number of projects increase? What is the total cost of ownership, including training, support, customizations etc. How does it fit your budget?
 
== Best practices <ref name = best_practices />==
 
== Advantages <ref name = history_pros_cons/>==
 
== Trade-offs for code reuse at various levels of components <ref name=trade_offs/>==
 
==Examples of Open Source Scrum tools==
The following shows a comparison of some agile project management tools.
<ref name = "Examples_of_open_source_scrum_tools" />
 
 
===Agilefant===
[[File:AgileFant.png|thumb|Agilefant's Development Porfolio|upright=1.25]]
[[File:AgileFant.png|thumb|Agilefant's Development Porfolio|upright=1.25]]
URL: http://www.agilefant.org/
Version reviewed: 1.6.2 
Technology: Tomcat 5.5, MySQL, Java 1.6
License: MIT
====Concepts====


=====Overview=====
Products are the highest level construct, and each deployment may have multiple products. Each product may have one or more projects, which are essentially releases. Each project may have one or more iterations. Each product, project (think "release"), and iteration has its own backlog, which contains stories. Stories can be moved to any other backlog, for example from the product backlog to an iteration backlog. Stories may consist of zero or more tasks. Projects can be prioritized in the Portfolio view.
Products are the highest level construct, and each deployment may have multiple products. Each product may have one or more projects, which are essentially releases. Each project may have one or more iterations. Each product, project (think "release"), and iteration has its own backlog, which contains stories. Stories can be moved to any other backlog, for example from the product backlog to an iteration backlog. Stories may consist of zero or more tasks. Projects can be prioritized in the Portfolio view.


The tool supports multiple concurrent iterations, which allows larger organizations to use the tool effectively.
The tool supports multiple concurrent iterations, which allows larger organizations to use the tool effectively.
Line 100: Line 73:
Version 1.6.2 does not include the concept of higher-level features or epics, although this feature is promised in version 2.0 which is supposed to be released soon. It does support the concept of themes, which are an attribute of stories, and this does provide a simplistic way to associate a group of stories.
Version 1.6.2 does not include the concept of higher-level features or epics, although this feature is promised in version 2.0 which is supposed to be released soon. It does support the concept of themes, which are an attribute of stories, and this does provide a simplistic way to associate a group of stories.


====Viability, Support & Documentation====
=====Strengths=====


The product documentation is adequate but not excellent. The product is intuitive enough that not much user documentation is necessary. The installation documentation is sufficient. Forums and email support appear to be fairly good. Development is active with version 2.0 supposed to be released soon, although no particular date for the release has been published.
*Rich feature set.
*Usability - Agilefant is intuitive.It lacks “[http://en.wikipedia.org/wiki/Drag_and_drop drag and drop]” features, but it otherwise makes good use of client-side features that make the user interface more responsive.
*Suitable for larger organizations and projects, except for the lack of “epics” or story hierarchies. (Version 2.0 should fix that shortcoming.)
*Reasonably intuitive and easy to use.
*Portfolio planning feature.
*Timesheet feature.


====Usability====
=====Weaknesses=====


Agilefant is intuitive. We were able to figure out how to use all features without relying on documentation. It lacks “drag and drop” features, but it otherwise makes good use of client-side features that make the user interface more responsive.
*Stories can be estimated in hours only, not points.
*Stories cannot be ranked absolutely; they can only be prioritized on a scale of 1 to 5.
*No “drag and drop” re-ordering of stories.
*No “epics” or hierarchy of stories. Note that a story hierarchy is promised for version 2.0.
*No “task board” or “whiteboard” view.
*No differentiation between user roles.


====Strengths====
===IceScrum<ref name = icescrum/>===
 
 
Rich feature set.
 
Suitable for larger organizations and projects, except for the lack of “epics” or story hierarchies. (Version 2.0 should fix that shortcoming.)
 
Reasonably intuitive and easy to use.
 
Portfolio planning feature.
 
Timesheet feature.
 
 
====Weaknesses====
 
 
Stories can be estimated in hours only, not points.
 
Stories cannot be ranked absolutely; they can only be prioritized on a scale of 1 to 5.
 
No “drag and drop” re-ordering of stories.
 
No “epics” or hierarchy of stories. Note that a story hierarchy is promised for version 2.0.
 
No “task board” or “whiteboard” view.
 
No differentiation between user roles.
 
 
====Overall Rating====
 
Agilefant is a very capable tool with a rich feature set and a few weaknesses. It is better suited for large projects and large organizations than any of the other tools reviewed in this article, but the lack of a hierarchy of story/requirement levels (a.k.a. "epics") is a significant drawback for large projects. The lack of epics or a hierarchy of stories, however, is a big weakness to overcome for large scale projects.
 
===IceScrum===
[[File:product_backlog_view.jpg|thumb|IceScrum's Product Backlog view|upright=1.25]]
[[File:product_backlog_view.jpg|thumb|IceScrum's Product Backlog view|upright=1.25]]
URL: http://www.icescrum.org/
Version reviewed: 2#13
Technology: Java 1.5 with servlet engine (e.g. Tomcat). Bundled with HSQLDB, but can be configured to work with other DBMs such as MySQL.
License: GPL
====Concepts====
Products (also called projects in some places) are the highest level construct, and each deployment may have multiple products. Each product has a single backlog and a roadmap. A backlog contains features (similar to epics), user stories, defects and technical stories. A roadmap contains multiple releases, each of which has a single release plan. A release plan consists of multiple sprints. Each sprint contains stories, which in turn contain tasks and acceptance tests. Impediments can be tracked for each product.


=====Overview=====
Products (also called projects in some places) are the highest level construct, and each deployment may have multiple products. Each product has a single [http://en.wikipedia.org/wiki/Scrum_%28development%29#Product_Backlog backlog] and a roadmap. A backlog contains features (similar to epics), [http://en.wikipedia.org/wiki/User_story user stories], defects and technical stories. A roadmap contains multiple releases, each of which has a single release plan. A release plan consists of multiple [http://en.wikipedia.org/wiki/Sprint_%28scrum%29#Sprint sprints]. Each sprint contains stories, which in turn contain tasks and acceptance tests. Impediments can be tracked for each product.


Unlike Agilefant, IceScrum includes a task board/whiteboard view of the iteration, allowing tasks to be dragged and dropped. It also allows drag and drop ranking of user stories in the backlog. Many options are available only from a right-click context menu, which isn’t obvious at first but is easy to use once you notice it.
Unlike Agilefant, IceScrum includes a task board/whiteboard view of the iteration, allowing tasks to be dragged and dropped. It also allows drag and drop ranking of [http://en.wikipedia.org/wiki/User_story user stories] in the backlog. Many options are available only from a right-click context menu, which isn’t obvious at first but is easy to use once you notice it.


IceScrum is the only product reviewed that has a planning poker feature. This feature allows a distributed team to play planning poker for estimating features and user stories.
IceScrum is the only product reviewed that has a planning poker feature. This feature allows a distributed team to play planning poker for estimating features and [http://en.wikipedia.org/wiki/User_story user stories].


IceScrum allows only a single release and single sprint to be active at one time (for a particular product), making it unsuitable for larger organizations that need multiple concurrent sprints with multiple teams running in parallel for a single product.
IceScrum allows only a single release and single sprint to be active at one time (for a particular product), making it unsuitable for larger organizations that need multiple concurrent sprints with multiple teams running in parallel for a single product.
Line 167: Line 107:
Beyond a burndown chart, IceScrum does not have any reports or reporting API.
Beyond a burndown chart, IceScrum does not have any reports or reporting API.


====Viability, Support & Documentation====
=====Strengths=====
 
*Rich feature set.
The product documentation is adequate but not excellent. The installation guide is written only in French. Forums and email support appear to be fairly good. Development is active.
*The Sprint Backlog view resembles a physical task board quite effectively.
 
*The Roadmap, Release Plan and Sprint Plan views support multiple levels of planning.
====Usability====
*Acceptance tests can be recorded for each story. A BDD-inspired template for acceptance tests is available.
 
*Includes a planning poker feature.
Some features are available only from right-click context menus. This is fine once you discover it, but it’s not obvious to new users. It has a relatively rich user interface with drag and drop capability in several places.
*Supports absolute ranking of stories by drag and drop, and estimates in story points.
 
*It has a relatively rich user interface with drag and drop capability in several places.
====Strengths====
 
 
Rich feature set.
 
The Sprint Backlog view resembles a physical task board quite effectively.
 
The Roadmap, Release Plan and Sprint Plan views support multiple levels of planning.
 
Acceptance tests can be recorded for each story. A BDD-inspired template for acceptance tests is available.
 
Includes a planning poker feature.
 
Supports absolute ranking of stories by drag and drop, and estimates in story points.
 
 
====Weaknesses====
 
 
The story card layout would make it difficult to rank a large product backlog.


Some features are not intuitive. Drag and drop works in some places but not in others, even though the mouse cursor make it seem that drag and drop should work. The right-click context menu is not obvious, but it's easy to use once you discover it.
=====Weaknesses=====
*The story card layout would make it difficult to rank a large product backlog.
*Some features are not intuitive. Drag and drop works in some places but not in others, even though the mouse cursor make it seem that drag and drop should work. The right-click context menu is not obvious, but it's easy to use once you discover it.
*IceScrum is not suitable for large projects with multiple teams working on a single product; only a single release and single sprint can be active at one time.


IceScrum is not suitable for large projects with multiple teams working on a single product; only a single release and single sprint can be active at one time.
===Agilo<ref name = agilo/>===
 
 
====Overall Rating====
 
IceScrum is a very capable tool with a rich feature set and a few weaknesses. Although it supports multiple products (projects), it is suitable only for small projects with a single team working on one sprint at a time per product.
 
===Agilo===
[[File:Agilos.png|thumb|Agilo's Sprint Backlog view|upright=1.25]]
[[File:Agilos.png|thumb|Agilo's Sprint Backlog view|upright=1.25]]
URL: http://www.agile42.com/cms/pages/agilo/


Version reviewed: 1.0.2 Pro (demo instance at https://agilo.agile42.com/login with login: demo/demo)
=====Overview=====
*Each deployment can have multiple milestones (releases). The backlog contains requirements, [http://en.wikipedia.org/wiki/User_story user stories] and tasks. These three item types support a hierarchy by reference: requirements can reference stories, and stories can reference tasks. This hierarchy is difficult to establish and utilize, however. Agilo has a separate backlog for defects, which makes it difficult to prioritize defects relative to [http://en.wikipedia.org/wiki/User_story user stories]. It also has a separate impediment backlog.
*Users can be given the roles of Scrum Master, Product Owner, or Team Member. Users may also be grouped into teams.
*Agilo includes an excellent and intuitive task board/whiteboard view of the iteration, allowing tasks to be dragged and dropped. This is by far the best feature of the tool; other features are less untuitive.
*Agilo has a simple dashboard with a sprint burndown chart, a graph of stories and tasks (total, planned, and closed), and allocation of tasks to team members by percent. In addition, it allows custom queries and reports to be created and saved.


Technology: Python (2.4, 2.5, or 2.6), SQLite (also PostgreSQL or MySQL). Built on Trac 0.11 (open source ticketing system built on Python).
=====Strengths=====
*Excellent task board/whiteboard iteration view with drag and drop functionality.
*Supports absolute ranking of stories by drag and drop, and estimates in story points.
*Good reporting features, including user-customized reports that can be saved.


License: Apache License 2.0
=====Weaknesses=====
*Some features are not intuitive. It feels like Trac didn’t support agile concepts very well so they had to be force-fit into Trac’s model.
*When creating a task, it can be associated with a sprint, but not with a story.
*Many operations require lots of clicks to complete.


====Concepts====
===eXplainPMT<ref name = explainpmt/>===
 
[[File:explainpmt.png|thumb|eXplainPMT's Backlog|upright=1.25]]
Each deployment can have multiple milestones (releases). The backlog contains requirements, user stories and tasks. These three item types support a hierarchy by reference: requirements can reference stories, and stories can reference tasks. This hierarchy is difficult to establish and utilize, however. Agilo has a separate backlog for defects, which makes it difficult to prioritize defects relative to user stories. It also has a separate impediment backlog.
 
Users can be given the roles of Scrum Master, Product Owner, or Team Member. Users may also be grouped into teams.
 
Agilo includes an excellent and intuitive task board/whiteboard view of the iteration, allowing tasks to be dragged and dropped. This is by far the best feature of the tool; other features are less untuitive. Perhaps Trac users would find it more friendly?
 
Agilo has a simple dashboard with a sprint burndown chart, a graph of stories and tasks (total, planned, and closed), and allocation of tasks to team members by percent. In addition, it allows custom queries and reports to be created and saved.
 
====Viability, Support & Documentation====
 
The product documentation is adequate but not excellent. The forums are very active and seem to be a good place for support. The Pro version includes professional support for about €8.50 per month.
 
====Usability====
 
I found some of Agilo’s features to be unintuitive and difficult to use, requiring many clicks and pages to accomplish common tasks. The task board/whiteboard feature, however, is excellent and very easy to use.
 
====Strengths====
 
 
Excellent task board/whiteboard iteration view with drag and drop functionality.
 
Supports absolute ranking of stories by drag and drop, and estimates in story points.
 
Good reporting features, including user-customized reports that can be saved.
 
====Weaknesses====
 
 
Some features are not intuitive. It feels like Trac didn’t support agile concepts very well so they had to be force-fit into Trac’s model.
 
When creating a task, it can be associated with a sprint, but not with a story.
 
Many operations require lots of clicks to complete.
 
 
====Overall Rating====
 
Although the task board/whiteboard view is intuitive and excellent, other features are less intuitive and often not very easy to use. The sprint burndown in the demo instance was flawed, showing 1200 hours when only 37 hours of tasks were planned.
 
===eXplainPMT===
 
URL: http://github.com/explainpmt/explainpmt/tree/master
 
Version reviewed: No version specified at demo site: http://github.com/explainpmt/explainpmt/tree/master (login: demo/demo)
 
Technology: Ruby, RDBMS (SQLite, PostgreSQL or MySQL)
 
License: GPL
 
====Concepts====


=====Overview=====
The highest level construct is the project, and eXplainPMT supports multiple projects. Each project has one or more releases, and iterations. Note that iterations are associated with projects, not with releases. A project has one backlog, and a backlog contains stories. Stories have tasks and acceptance tests, and can be assigned to a release. Stories may also be associated with an initiative, which is somewhat like an epic, except initiatives cannot be ranked or prioritized. Surprisingly, tasks do not have estimated or actual hours; they have only two states: incomplete or complete.
The highest level construct is the project, and eXplainPMT supports multiple projects. Each project has one or more releases, and iterations. Note that iterations are associated with projects, not with releases. A project has one backlog, and a backlog contains stories. Stories have tasks and acceptance tests, and can be assigned to a release. Stories may also be associated with an initiative, which is somewhat like an epic, except initiatives cannot be ranked or prioritized. Surprisingly, tasks do not have estimated or actual hours; they have only two states: incomplete or complete.


Users in eXplainPMT do not have specific roles; all users are the same. Users may be grouped into teams.
Users in eXplainPMT do not have specific roles; all users are the same. Users may be grouped into teams.
Line 277: Line 152:
eXplainPMT has no user guide and only a brief README file for an installation guide. It has no forums, nor any email support. It is unclear whether development is still active; the last update was November 2008.
eXplainPMT has no user guide and only a brief README file for an installation guide. It has no forums, nor any email support. It is unclear whether development is still active; the last update was November 2008.


====Usability====
=====Strengths=====
*Intuitive interface.
*Supports the definition of acceptance tests for stories.


The user interface is straightforward and intuitive, but some very basic features are lacking. For example, after creating a story in the backlog, it cannot be moved into an iteration. In addition, eXplainPMT does not support drag and drop nor the richer experience of modern browser applications.
=====Weaknesses=====
*Cannot estimate or track task hours!
*No task board/whiteboard view.
*No iteration burndown chart.
*No releases or roadmap.
*Development status is unclear; the last update was November 2008.
*Support and documentation are almost non-existent.
*Not suitable for large projects since it allows only one iteration to be active at a time.


====Strengths====
===XPlanner<ref name = xplanner/>===
[[File:xplanner.png|thumb|XPlanner's Story view|upright=1.25]]


=====Overview=====
The highest level construct is the project, and XPlanner supports multiple projects. It does not include releases. Each project has one or more iterations. It does not include a product backlog, but a workaround is to create a special iteration to use as a product backlog. Iterations contain stories, and stories contain tasks. Tasks may be of type feature, debt, defect, ftest (functional test), atest (acceptance test), or overhead. Stories are estimated in hours, and tasks are estimated and tracked in hours.


Intuitive interface.
Users in XPlanner can be assigned four permission levels: Viewer (read only), Editor, Admin., or Super Admin. XPlanner does not have a team construct for grouping users.


Supports the definition of acceptance tests for stories.
=====Strengths=====
*Intuitive interface.
*Rich built-in reports and charts.
*[http://en.wikipedia.org/wiki/SOAP SOAP API] for integration.
*Customizable notation for simple URL linking with external systems such as defect tracking.


=====Weaknesses=====
*No releases or roadmap.
*No task board/whiteboard view.
*No story points.
*No "epics" or hierarchy of stories/features/requirements.
*The project is dormant, with the last update in May 2006.
*Support is very limited since the project is dormant.


====Weaknesses====
===Quick Comparison===
<table border=2>
  <tr>
    <th>'''        '''</th>
    <th>'''Agilefant'''</th>
    <th>'''IceScrum'''</th>
    <th>'''Agilo'''</th>
    <th>'''eXPlainPMT'''</th>
    <th>'''XPlanner'''</th>


  </tr>
  <tr>
    <td>''User roles''</td>
    <td>None</td>
    <td>PO, SM, Team Member, Stakeholder, plus custom roles.</td>
    <td>SM, PO, Team Member.</td>
    <td>None</td>
    <td>Viewer, Editor, Admin, Super Admin.</td>
  </tr>
  <tr>
    <td>''Reports''</td>
    <td>Timesheets only</td>
    <td>None</td>
    <td>Can save customized reports</td>
    <td>None</td>
    <td>Extensive built-in reports, but no custom reporting</td>
  </tr>
<tr>
    <td>''Integration & API(s)''</td>
    <td>None</td>
    <td>None</td>
    <td>SVN, trac, mylyn</td>
    <td>None</td>
    <td>SOAP, notation for URL linking</td>
  </tr>
<tr>
    <td>''Pros''</td>
    <td>Rich feature set. Timesheet feature.</td>
    <td>Rich feature set. Good task board view. Planning poker feature</td>
    <td>Great whiteboard view</td>
    <td>Intuitive</td>
    <td>Intuitive. Rich charts and reports built in</td>
  </tr>
<tr>
    <td>''Cons''</td>
    <td>No task board view</td>
    <td>Not always intuitive. Not suitable for large projects</td>
    <td>Some common actions require lots of clicks</td>
    <td>No support or forums. Status uncertain. No hours for tasks. No sprint burndown</td>
    <td>Inactive and Not supported. Not suitable for large projects. Doesn’t directly support releases/roadmaps.</td>
  </tr>
</table>


Cannot estimate or track task hours!
==Examples of proprietary Scrum Tools==
Here are some of the examples of proprietary scrum project management tools -


No task board/whiteboard view.
===IBM Rational Team Concert<ref name = IBM_RTC/>===
[[File:rtc.png|thumb|Planned Items View|upright=1.25]]


No iteration burndown chart.
=====Concepts=====
IBM Rational Team Concert is built on the [http://en.wikipedia.org/wiki/Jazz_%28computer%29 Jazz Platform], an extensible technology platform that helps teams integrate tasks across the software life cycle.
Rational Team Concert is built on a client-server architecture and it enables software development teams to track all aspects of their work, such as work items, source control, reporting, and build management, in a single product. Rational Team Concert integrates with several other products, including Subversion, Git, and IBM Rational ClearCase revision-control products, IBM Rational ClearQuest and JIRA change management products, IBM Rational Quality Manager and HP Quality Center quality management systems, and IBM Rational Build Forge, Hudson, CruiseControl, and Maven build and process automation tools.
Rational Team Concert has an Eclipse-based client interface, a Microsoft Visual Studio client interface, and a Web interface. Additionally it provides since version 4.0 a windows shell integration within the Windows Explorer for source control of files within the Rational Team Concert repository. The client interfaces provide an integrated development environment for developers to build and deliver artifacts. Users can use the Web interface to administer servers and projects, access project areas, browse repository information, update tasks, or read about recent events.


No releases or roadmap.
=====Strengths=====


Development status is unclear; the last update was November 2008.
* User friendly interface
* Does a great job with managing changesets
* It integrates the support lifecycle into the rest of the Agile development process


Support and documentation are almost non-existent.
=====Weaknesses=====


Not suitable for large projects since it allows only one iteration to be active at a time.
*Cannot use it free of charge anymore
*It's license is pretty expensive.


===JIRA<ref name = Jira_wiki/>===
[[File:jira.png|thumb|Jira's Dashboard View|upright=1.25]]


====Overall Rating====
=====Concepts=====
JIRA is a proprietary issue tracking product, developed by Atlassian, commonly used for bug tracking, issue tracking, and project management. The product name, JIRA, is not an acronym but rather a truncation of "Gojira", the Japanese name for Godzilla.It has been developed since 2002.
JIRA is a commercial software product that can be licensed for running on-premises or available as a hosted application. Pricing depends on the maximum number of users, with approximately $50 per user for in-house and $7 per month per user for the hosted version being typical prices.
Atlassian provides JIRA for free to open source projects that meet certain criteria, and organizations that are non-profit, non-government, non-academic, non-commercial, non-political, and secular.
For academic and commercial customers, the full source code is available under a developer source license.
Starting with JIRA 4, a 10-user starter license costs $10 with all proceeds benefiting Room to Read.Starter licenses are also available for other Atlassian products that can integrate with JIRA, such as Bonfire, Confluence, Crucible, GreenHopper, Bamboo, FishEye and Crowd.


eXplainPMT is missing many important features, the development status is uncertain, and support and documentation are almost non-existent. It does not support large teams. Agilefant, IceScrum, Agilo and XPlanner are all likely to be better tools for most agile teams.
=====Strengths<ref name = Jira_mozilla_wiki/>=====


*Like Agile bench, Jira seems very usable and very straightforward
*Jira includes Grasshopper, a tool that provides features useful to Scrum teams. Grasshopper provides a product backlog, sprint backlogs, a burndown chart, and various other statistics.


===XPlanner===
=====Weaknesses=====


XPlanner is included in this comparison because at one time it had a large user base and was the primary tool in this category. Although the project is dormant now, it serves as a good baseline for seeing how tools have changed in the past few years.
*Jira is not free


===Mingle<ref name = Mingle/>===
[[File:mingle.png|thumb|Mingle's Sprint View|upright=1.25]]


URL: http://www.xplanner.org/
=====Concepts<ref name = Mingle_scrumtools/>=====
Mingle and Mingle Plus are a proprietary project management and collaboration platform that is built by ThoughtWorks Studios, the software division of ThoughtWorks. Mingle and Mingle Plus provide ways for a team to share information about a project and as a system of record and management for the project itself. Mingle and Mingle Plus show the status and progress of project tasks on drag and drop Card Walls that are meant to simulate an Agile Story Wall, has wikis for project collaboration, and can associate instant messages with project tasks through a feature Mingle calls Murmurs. Mingle and Mingle Plus can generate burn-down charts showing work remaining, velocity charts showing actual versus expected progress, and pivot tables for grouping data by one or more attributes.
Mingle Plus plus features include: Create visual, interactive timelines to communicate your organization's plans and goals. Collaborate to plan work towards common objectives. Track progress towards goals, understand the current status of projects and objectives. Forecast completion dates based on project work. Understand when forecasts differ from plans. Replan and adapt to change. Get alerted when objectives may be delivered later than expected. Understand which projects and work items are at risk. Work together to resolve issues.


Version reviewed: 0.7b (beta)
Mingle and Mingle Plus are intended to support various flavors of Agile like XP, Scrum, Agile Hybrid. Though primarily a project management tool, it also provides bug tracking, project reporting and program management capabilities.


Technology: Java 1.5, Tomcat 5.0 (not 5.5), MySQL
=====Strengths=====


License: LGPL
*Although creating a project from the scratch on Mingle can be a tough task, there is a Scrum project template ready to be used.
*It’s also possible to create custom properties for each type of release so one can define all kinds of information one needs for your items and these properties can also be an aggregation of properties from the level below.
*The project structure on Mingle can be totally customized even with more than one structure in the same project, here called card trees.
*The Sprint backlog tab is good for the daily meeting and emulates the taskboard, the drag and drop feature really helps to create an immediate link to the mechanics of a taskboard on the wall.


====Concepts====
=====Weaknesses=====


The highest level construct is the project, and XPlanner supports multiple projects. It does not include releases. Each project has one or more iterations. It does not include a product backlog, but a workaround is to create a special iteration to use as a product backlog. Iterations contain stories, and stories contain tasks. Tasks may be of type feature, debt, defect, ftest (functional test), atest (acceptance test), or overhead. Stories are estimated in hours, and tasks are estimated and tracked in hours.
*There are a lot of customizations and expansion points but they are not really accessible.
*The feeling is that without the templates it would need a lot of work to create something really useful for a Scrum team.


== Conclusion ==


Users in XPlanner can be assigned four permission levels: Viewer (read only), Editor, Admin., or Super Admin. XPlanner does not have a team construct for grouping users.
To summarize, a tool for distributed teams helps improve communication and increase stakeholder visibility into the project. There are many open source and proprietary scrum tools available in the market. A team can decide on which scrum tool to select depending on the requirements.
 
====Viability, Support & Documentation====
 
The last update to XPlanner was in May 2006, so it’s safe to say the project is dormant. The project does have forums for support that contain lots of useful help but they are inactive now; the forum averages two new topics per month with a few replies each. The installation documentation is sufficient although it’s only a README file in the latest version 0.7b. User documentation is minimal, but the tool is intuitive enough that little documentation is necessary.
 
====Usability====
 
XPlanner’s UI is straightforward and intuitive. However, it lacks most of the client-side (AJAX-based) usability features of most modern browser applications.
 
====Strengths====
 
 
Intuitive interface.
 
Rich built-in reports and charts.
 
SOAP API for integration.
 
Customizable notation for simple URL linking with external systems such as defect tracking.
 
 
====Weaknesses====
 
 
No releases or roadmap.
 
No task board/whiteboard view.
 
No story points.
 
No "epics" or hierarchy of stories/features/requirements.
 
The project is dormant, with the last update in May 2006.
 
Support is very limited since the project is dormant.


==See Also==


====Overall Rating====
* http://agilescout.com/best-agile-scrum-tools/
 
* http://www.agilebuddy.com/
Despite its shortcomings, XPlanner is still a good tool for small teams. Since the project is dormant and other tools have better features now, we recommend Agilefant, IceScrum or Agilo over XPlanner, but recommend XPlanner over eXPlainPMT for most teams.
* http://www.versionone.com/scrum-tools/
 
* http://borisgloger.com/2009/01/21/scrum-tools-projectcards-review/
== Conclusion ==
* http://borisgloger.com/2009/04/06/scrum-tools-scrumninja-review/
 
* http://borisgloger.com/2008/11/15/scrum-tools-scrumy-pro-review-update/
==See also==
* http://borisgloger.com/scrum/scrum-flow/
*[http://en.wikipedia.org/wiki/Don%27t_repeat_yourself Don't repeat yourself]


== References ==
== References ==
<references>
<references>


<ref name = techniques> http://www.revision-zero.org/reuse</ref>
<ref name = Examples_of_open_source_scrum_tools> http://www.openlogic.com/wazi/bid/188152/Comparing-Open-Source-Agile-Project-Management-Tools</ref>
<ref name = Examples_of_open_source_scrum_tools> http://www.openlogic.com/wazi/bid/188152/Comparing-Open-Source-Agile-Project-Management-Tools</ref>
<ref name = Scrum> http://en.wikipedia.org/wiki/Scrum_(development)</ref>
<ref name = Scrum> http://en.wikipedia.org/wiki/Scrum_(development)</ref>
<ref name = Selecting_the_tool> http://toolsforagile.com/blog/archives/160/agile-project-management-tool-evaluation-guide</ref>
<ref name = Selecting_the_tool> http://toolsforagile.com/blog/archives/160/agile-project-management-tool-evaluation-guide</ref>
<ref name = simple_scrum_tools> http://www.agilemodeling.com/essays/simpleTools.htm</ref>
<ref name = iterative>http://en.wikipedia.org/wiki/Iterative_and_incremental_development</ref>
<ref name = agilefant>http://www.agilefant.org/</ref>
<ref name = icescrum>http://www.icescrum.org/</ref>
<ref name = xplanner>http://www.xplanner.org/</ref>
<ref name = agilo>http://www.agile42.com/cms/pages/agilo/</ref>
<ref name = explainpmt>http://github.com/explainpmt/explainpmt/tree/master</ref>
<ref name = Jira_wiki> http://en.wikipedia.org/wiki/JIRA</ref>
<ref name = Jira_mozilla_wiki>https://wiki.mozilla.org/Scrum/Tools</ref>
<ref name = IBM_RTC>http://en.wikipedia.org/wiki/IBM_Rational_Team_Concert</ref>
<ref name = Mingle>http://en.wikipedia.org/wiki/Mingle</ref>
<ref name = Mingle_scrumtools>http://borisgloger.com/2008/08/26/scrumtools-mingle/</ref>
</references>
</references>

Latest revision as of 19:22, 1 November 2012

Scrum Tools - This page gives survey of the tools that can be used for practicing scrum. It considers the features offered by each of them, the scenarios in which each of them can be used considering what features it has and what features it lacks, cost involved etc.

Overview <ref name = "Scrum" />

Scrum

Scrum is an iterative and incremental agile software development<ref name = "iterative" /> method for managing software projects and products or application development. Scrum focuses on project management institutions where it is difficult to plan ahead. Mechanisms of empirical process control, where feedback loops that constitute the core management technique are used as opposed to traditional command-and-control oriented management. It represents a radically new approach for planning and managing projects, bringing decision-making authority to the level of operation properties and certainties.

Scrum Tools

Scrum can be implemented through a wide range of tools. Many companies use universal tools, such as spreadsheets to build and maintain artifacts such as the sprint backlog. There are also open-source and proprietary packages dedicated to management of products under the Scrum process. Other organizations implement Scrum without the use of any tools and maintain their artifacts in hard-copy forms such as paper, whiteboards and sticky notes.

Selecting The Right Tool <ref name = Selecting_the_tool/>

Here are some of the factors which should be considered before selecting the correct scrum tool -

Primary Factors

  • Does the tool improve visibility?

- Scrum requires transparency to succeed. Everyone who needs to know about the project from the developers to the stakeholders and maybe even the customer should be able to use the tool. There is no point using a tool if only a Scrum Master or a few people can use it and everyone else has to rely on email.

  • Does the tool improve communication?

- Tools can be used to open up channels of communication. For example, allowing a developer to comment on a user story and have a remote customer reply back – setting up direct communication between developer and customer and bypassing all the bureaucracy in the middle.

  • Does the tool reinforce trust?

- Example: A team member forgot to update the estimate for Friday. He remembers on Monday. Can you set the estimate for Friday on Monday? In a “high trust” tool like pen & paper: you can just pick up a pen and redraw the burndown. In a “low trust” tool, you cannot do this because it is considered as meddling with the past recorded history of actions.

  • Does the tool adapt to the way you work?

- Each team is going to use the tool differently. Some tools adapt to the way you work, other tools force you to work the way the tool is setup. Because of the self-managed nature of scrum, it is important that the tool support the team, and the team should not have to change their working to fit the tool.

Secondary Factors

  • Standalone, monolithic or integrated :

- Standalone tools let you create users, stories, iterations and tasks and generate some reports like burndown or velocity. Basic, but useful when you want something simple.

- Integrated tools do only project management, but they can integrate with external tools like other bug tracking tools, source control, wikis and so on. For example, you will be able to synchronize bugs from the bug tracker to the PM tool or link tasks in the tool with code commits and so on. They can provide an overview across multiple tools in use.

- Monolithic tools support the entire life-cycle like document management, bug tracking, artifact management over and above standard PM functionality all within a single tool. Advantages of monolithic are that all components are tightly integrated. Disadvantage is that you have to discard all your existing tools to move to a monolithic one. Also if the monolithic tool does not support a particular component (like continuous integration or code analysis) you may still have to use multiple tools.

  • Usability :

- How usable is the tool? When you have poor usability, people may resent working with the tool and might start working around the tool instead. Tools with poor usability may also call for additional unplanned expenditure in training and support. You also have issues of general resentment by the team at whoever foisted the tool upon them.

  • Pricing model :

- Is the tool open source, free or commercial? For commercial tools, it the pricing per-user or per-project? Subscription or one-time payment? What is your risk exposure should the team size or number of projects increase? What is the total cost of ownership, including training, support, customizations etc. How does it fit your budget?

Low Tech Scrum Tools<ref name = simple_scrum_tools/>

  • Index cards :

- The eXtreme Programming (XP) community swears by the use of standard index cards for a wide variety of modeling techniques, and in particular Class Responsibility Collaborator (CRC) modeling.

  • Post-It notes :

- Post-It notes are also an option, for example one can develop an abstract/essential user interface prototype using Post-Its on large sheets of paper. This is part of a technique called essential user interface modeling.

  • Paper :

- Pieces of paper, or index cards, tacked onto a whiteboard and connected by strings can be used for a wide variety of models. For example the individual sheets of paper can represent database tables and the lines relationships between tables on a physical data model, or the sheets can represent screens and the strings navigation flows between screens on a user interface flow diagram, or the sheets can represent use cases and actors and the strings represent associations between them on a UML use case diagram.

  • Plain old whiteboards (POWs) :

- A whiteboard for sketching on is likely the most common modeling tool in use. A digital camera can easily make copies of sketches that one wants to keep.

Examples of Open Source Scrum Tools<ref name = "Examples_of_open_source_scrum_tools" />

Here are some of the examples of open-source scrum project management tools -

Agilefant<ref name = agilefant/>

Agilefant's Development Porfolio
Overview

Products are the highest level construct, and each deployment may have multiple products. Each product may have one or more projects, which are essentially releases. Each project may have one or more iterations. Each product, project (think "release"), and iteration has its own backlog, which contains stories. Stories can be moved to any other backlog, for example from the product backlog to an iteration backlog. Stories may consist of zero or more tasks. Projects can be prioritized in the Portfolio view.

The tool supports multiple concurrent iterations, which allows larger organizations to use the tool effectively.

Agilefant supports multiple users and users can be grouped into teams. However, it does not support any user roles; a user is a user, with no differences in permissions or access to features. Teams can be assigned to specific iterations.

Version 1.6.2 does not include the concept of higher-level features or epics, although this feature is promised in version 2.0 which is supposed to be released soon. It does support the concept of themes, which are an attribute of stories, and this does provide a simplistic way to associate a group of stories.

Strengths
  • Rich feature set.
  • Usability - Agilefant is intuitive.It lacks “drag and drop” features, but it otherwise makes good use of client-side features that make the user interface more responsive.
  • Suitable for larger organizations and projects, except for the lack of “epics” or story hierarchies. (Version 2.0 should fix that shortcoming.)
  • Reasonably intuitive and easy to use.
  • Portfolio planning feature.
  • Timesheet feature.
Weaknesses
  • Stories can be estimated in hours only, not points.
  • Stories cannot be ranked absolutely; they can only be prioritized on a scale of 1 to 5.
  • No “drag and drop” re-ordering of stories.
  • No “epics” or hierarchy of stories. Note that a story hierarchy is promised for version 2.0.
  • No “task board” or “whiteboard” view.
  • No differentiation between user roles.

IceScrum<ref name = icescrum/>

IceScrum's Product Backlog view
Overview

Products (also called projects in some places) are the highest level construct, and each deployment may have multiple products. Each product has a single backlog and a roadmap. A backlog contains features (similar to epics), user stories, defects and technical stories. A roadmap contains multiple releases, each of which has a single release plan. A release plan consists of multiple sprints. Each sprint contains stories, which in turn contain tasks and acceptance tests. Impediments can be tracked for each product.

Unlike Agilefant, IceScrum includes a task board/whiteboard view of the iteration, allowing tasks to be dragged and dropped. It also allows drag and drop ranking of user stories in the backlog. Many options are available only from a right-click context menu, which isn’t obvious at first but is easy to use once you notice it.

IceScrum is the only product reviewed that has a planning poker feature. This feature allows a distributed team to play planning poker for estimating features and user stories.

IceScrum allows only a single release and single sprint to be active at one time (for a particular product), making it unsuitable for larger organizations that need multiple concurrent sprints with multiple teams running in parallel for a single product.

IceScrum users may have any of the Scrum roles (Product Owner, Scrum Master, Team Member, Stakeholder) plus custom roles may be created. It does not allow users to be grouped into teams.

Beyond a burndown chart, IceScrum does not have any reports or reporting API.

Strengths
  • Rich feature set.
  • The Sprint Backlog view resembles a physical task board quite effectively.
  • The Roadmap, Release Plan and Sprint Plan views support multiple levels of planning.
  • Acceptance tests can be recorded for each story. A BDD-inspired template for acceptance tests is available.
  • Includes a planning poker feature.
  • Supports absolute ranking of stories by drag and drop, and estimates in story points.
  • It has a relatively rich user interface with drag and drop capability in several places.
Weaknesses
  • The story card layout would make it difficult to rank a large product backlog.
  • Some features are not intuitive. Drag and drop works in some places but not in others, even though the mouse cursor make it seem that drag and drop should work. The right-click context menu is not obvious, but it's easy to use once you discover it.
  • IceScrum is not suitable for large projects with multiple teams working on a single product; only a single release and single sprint can be active at one time.

Agilo<ref name = agilo/>

Agilo's Sprint Backlog view
Overview
  • Each deployment can have multiple milestones (releases). The backlog contains requirements, user stories and tasks. These three item types support a hierarchy by reference: requirements can reference stories, and stories can reference tasks. This hierarchy is difficult to establish and utilize, however. Agilo has a separate backlog for defects, which makes it difficult to prioritize defects relative to user stories. It also has a separate impediment backlog.
  • Users can be given the roles of Scrum Master, Product Owner, or Team Member. Users may also be grouped into teams.
  • Agilo includes an excellent and intuitive task board/whiteboard view of the iteration, allowing tasks to be dragged and dropped. This is by far the best feature of the tool; other features are less untuitive.
  • Agilo has a simple dashboard with a sprint burndown chart, a graph of stories and tasks (total, planned, and closed), and allocation of tasks to team members by percent. In addition, it allows custom queries and reports to be created and saved.
Strengths
  • Excellent task board/whiteboard iteration view with drag and drop functionality.
  • Supports absolute ranking of stories by drag and drop, and estimates in story points.
  • Good reporting features, including user-customized reports that can be saved.
Weaknesses
  • Some features are not intuitive. It feels like Trac didn’t support agile concepts very well so they had to be force-fit into Trac’s model.
  • When creating a task, it can be associated with a sprint, but not with a story.
  • Many operations require lots of clicks to complete.

eXplainPMT<ref name = explainpmt/>

eXplainPMT's Backlog
Overview

The highest level construct is the project, and eXplainPMT supports multiple projects. Each project has one or more releases, and iterations. Note that iterations are associated with projects, not with releases. A project has one backlog, and a backlog contains stories. Stories have tasks and acceptance tests, and can be assigned to a release. Stories may also be associated with an initiative, which is somewhat like an epic, except initiatives cannot be ranked or prioritized. Surprisingly, tasks do not have estimated or actual hours; they have only two states: incomplete or complete.

Users in eXplainPMT do not have specific roles; all users are the same. Users may be grouped into teams.

Viability, Support & Documentation

eXplainPMT has no user guide and only a brief README file for an installation guide. It has no forums, nor any email support. It is unclear whether development is still active; the last update was November 2008.

Strengths
  • Intuitive interface.
  • Supports the definition of acceptance tests for stories.
Weaknesses
  • Cannot estimate or track task hours!
  • No task board/whiteboard view.
  • No iteration burndown chart.
  • No releases or roadmap.
  • Development status is unclear; the last update was November 2008.
  • Support and documentation are almost non-existent.
  • Not suitable for large projects since it allows only one iteration to be active at a time.

XPlanner<ref name = xplanner/>

XPlanner's Story view
Overview

The highest level construct is the project, and XPlanner supports multiple projects. It does not include releases. Each project has one or more iterations. It does not include a product backlog, but a workaround is to create a special iteration to use as a product backlog. Iterations contain stories, and stories contain tasks. Tasks may be of type feature, debt, defect, ftest (functional test), atest (acceptance test), or overhead. Stories are estimated in hours, and tasks are estimated and tracked in hours.

Users in XPlanner can be assigned four permission levels: Viewer (read only), Editor, Admin., or Super Admin. XPlanner does not have a team construct for grouping users.

Strengths
  • Intuitive interface.
  • Rich built-in reports and charts.
  • SOAP API for integration.
  • Customizable notation for simple URL linking with external systems such as defect tracking.
Weaknesses
  • No releases or roadmap.
  • No task board/whiteboard view.
  • No story points.
  • No "epics" or hierarchy of stories/features/requirements.
  • The project is dormant, with the last update in May 2006.
  • Support is very limited since the project is dormant.

Quick Comparison

Agilefant IceScrum Agilo eXPlainPMT XPlanner
User roles None PO, SM, Team Member, Stakeholder, plus custom roles. SM, PO, Team Member. None Viewer, Editor, Admin, Super Admin.
Reports Timesheets only None Can save customized reports None Extensive built-in reports, but no custom reporting
Integration & API(s) None None SVN, trac, mylyn None SOAP, notation for URL linking
Pros Rich feature set. Timesheet feature. Rich feature set. Good task board view. Planning poker feature Great whiteboard view Intuitive Intuitive. Rich charts and reports built in
Cons No task board view Not always intuitive. Not suitable for large projects Some common actions require lots of clicks No support or forums. Status uncertain. No hours for tasks. No sprint burndown Inactive and Not supported. Not suitable for large projects. Doesn’t directly support releases/roadmaps.

Examples of proprietary Scrum Tools

Here are some of the examples of proprietary scrum project management tools -

IBM Rational Team Concert<ref name = IBM_RTC/>

Planned Items View
Concepts

IBM Rational Team Concert is built on the Jazz Platform, an extensible technology platform that helps teams integrate tasks across the software life cycle. Rational Team Concert is built on a client-server architecture and it enables software development teams to track all aspects of their work, such as work items, source control, reporting, and build management, in a single product. Rational Team Concert integrates with several other products, including Subversion, Git, and IBM Rational ClearCase revision-control products, IBM Rational ClearQuest and JIRA change management products, IBM Rational Quality Manager and HP Quality Center quality management systems, and IBM Rational Build Forge, Hudson, CruiseControl, and Maven build and process automation tools. Rational Team Concert has an Eclipse-based client interface, a Microsoft Visual Studio client interface, and a Web interface. Additionally it provides since version 4.0 a windows shell integration within the Windows Explorer for source control of files within the Rational Team Concert repository. The client interfaces provide an integrated development environment for developers to build and deliver artifacts. Users can use the Web interface to administer servers and projects, access project areas, browse repository information, update tasks, or read about recent events.

Strengths
  • User friendly interface
  • Does a great job with managing changesets
  • It integrates the support lifecycle into the rest of the Agile development process
Weaknesses
  • Cannot use it free of charge anymore
  • It's license is pretty expensive.

JIRA<ref name = Jira_wiki/>

Jira's Dashboard View
Concepts

JIRA is a proprietary issue tracking product, developed by Atlassian, commonly used for bug tracking, issue tracking, and project management. The product name, JIRA, is not an acronym but rather a truncation of "Gojira", the Japanese name for Godzilla.It has been developed since 2002. JIRA is a commercial software product that can be licensed for running on-premises or available as a hosted application. Pricing depends on the maximum number of users, with approximately $50 per user for in-house and $7 per month per user for the hosted version being typical prices. Atlassian provides JIRA for free to open source projects that meet certain criteria, and organizations that are non-profit, non-government, non-academic, non-commercial, non-political, and secular. For academic and commercial customers, the full source code is available under a developer source license. Starting with JIRA 4, a 10-user starter license costs $10 with all proceeds benefiting Room to Read.Starter licenses are also available for other Atlassian products that can integrate with JIRA, such as Bonfire, Confluence, Crucible, GreenHopper, Bamboo, FishEye and Crowd.

Strengths<ref name = Jira_mozilla_wiki/>
  • Like Agile bench, Jira seems very usable and very straightforward
  • Jira includes Grasshopper, a tool that provides features useful to Scrum teams. Grasshopper provides a product backlog, sprint backlogs, a burndown chart, and various other statistics.
Weaknesses
  • Jira is not free

Mingle<ref name = Mingle/>

Mingle's Sprint View
Concepts<ref name = Mingle_scrumtools/>

Mingle and Mingle Plus are a proprietary project management and collaboration platform that is built by ThoughtWorks Studios, the software division of ThoughtWorks. Mingle and Mingle Plus provide ways for a team to share information about a project and as a system of record and management for the project itself. Mingle and Mingle Plus show the status and progress of project tasks on drag and drop Card Walls that are meant to simulate an Agile Story Wall, has wikis for project collaboration, and can associate instant messages with project tasks through a feature Mingle calls Murmurs. Mingle and Mingle Plus can generate burn-down charts showing work remaining, velocity charts showing actual versus expected progress, and pivot tables for grouping data by one or more attributes. Mingle Plus plus features include: Create visual, interactive timelines to communicate your organization's plans and goals. Collaborate to plan work towards common objectives. Track progress towards goals, understand the current status of projects and objectives. Forecast completion dates based on project work. Understand when forecasts differ from plans. Replan and adapt to change. Get alerted when objectives may be delivered later than expected. Understand which projects and work items are at risk. Work together to resolve issues.

Mingle and Mingle Plus are intended to support various flavors of Agile like XP, Scrum, Agile Hybrid. Though primarily a project management tool, it also provides bug tracking, project reporting and program management capabilities.

Strengths
  • Although creating a project from the scratch on Mingle can be a tough task, there is a Scrum project template ready to be used.
  • It’s also possible to create custom properties for each type of release so one can define all kinds of information one needs for your items and these properties can also be an aggregation of properties from the level below.
  • The project structure on Mingle can be totally customized even with more than one structure in the same project, here called card trees.
  • The Sprint backlog tab is good for the daily meeting and emulates the taskboard, the drag and drop feature really helps to create an immediate link to the mechanics of a taskboard on the wall.
Weaknesses
  • There are a lot of customizations and expansion points but they are not really accessible.
  • The feeling is that without the templates it would need a lot of work to create something really useful for a Scrum team.

Conclusion

To summarize, a tool for distributed teams helps improve communication and increase stakeholder visibility into the project. There are many open source and proprietary scrum tools available in the market. A team can decide on which scrum tool to select depending on the requirements.

See Also

References

<references>

<ref name = Examples_of_open_source_scrum_tools> http://www.openlogic.com/wazi/bid/188152/Comparing-Open-Source-Agile-Project-Management-Tools</ref> <ref name = Scrum> http://en.wikipedia.org/wiki/Scrum_(development)</ref> <ref name = Selecting_the_tool> http://toolsforagile.com/blog/archives/160/agile-project-management-tool-evaluation-guide</ref> <ref name = simple_scrum_tools> http://www.agilemodeling.com/essays/simpleTools.htm</ref> <ref name = iterative>http://en.wikipedia.org/wiki/Iterative_and_incremental_development</ref> <ref name = agilefant>http://www.agilefant.org/</ref> <ref name = icescrum>http://www.icescrum.org/</ref> <ref name = xplanner>http://www.xplanner.org/</ref> <ref name = agilo>http://www.agile42.com/cms/pages/agilo/</ref> <ref name = explainpmt>http://github.com/explainpmt/explainpmt/tree/master</ref> <ref name = Jira_wiki> http://en.wikipedia.org/wiki/JIRA</ref> <ref name = Jira_mozilla_wiki>https://wiki.mozilla.org/Scrum/Tools</ref> <ref name = IBM_RTC>http://en.wikipedia.org/wiki/IBM_Rational_Team_Concert</ref> <ref name = Mingle>http://en.wikipedia.org/wiki/Mingle</ref> <ref name = Mingle_scrumtools>http://borisgloger.com/2008/08/26/scrumtools-mingle/</ref> </references>

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2012/ch2a_2w7_ma&oldid=69396"