Post on 08-May-2015
description
Current and Future of Agile PM Tools
Syed Rayhan, Nimat Haque
Co-founders, Code71, Inc.
Product: http://www.scrumpad.com
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
2
Syed Rayhan’s Background
Expertise
Career
Iterative incremental development
Technology planning and architecture
On-shore/Off-shore software development using Agile/Scrum
Interests
Co-founder, Code71, Inc.
14+ years of total experience
Co-author of “Enterprise Java with UML”
Cultural aspect of self-organizing team
Scrum for projects delivered remotely
Agile engineering practices
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
3
Nimat Haque’s Background
Expertise
Career
Project Management
On-shore/Off-shore software development using Agile/Scrum
Interests
Co-founder, Code71, Inc.
Current job: Scrum Master at INPUT in Reston, VA
10+ years of total experience
Lean Software Engineering – Learning about Kanban
Coaching
Distributed Teams – how to get best out of remote teams
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
4
The tool questions?
What kind of tool is good for my team?
What options are available?
Is a tool necessary for Agile adoption?
When is a simple whiteboard+card+marker good for team?
When is spreadsheet good for a team?
Do I need a tool?
What is the future trend for Agile PM tools?
Can I adopt traditional tool for Agile projects?
What features should an Agile PM tool have?
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
5
What do we expect from a tool?
Story/Bug/Task tracking
Burndown charts
Estimation tracking
Product Backlog Management
Minimum Viable Product Additional/Enterprise Features
Test case management
Release planning
Security/Backup
Conversation/Context tracking
Reporting
Change history tracking
Notification
Program/Portfolio planning
Documentation
Status tracking
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
6
Available options for tools
Simple Tool Whiteboard + Corkboard + Card + Flip charts +Marker
Spread sheet Excel with agile templates
Traditional PMTool
MS Project +MS Project Server, TFS, Clarity, Basecamp
Agile PM Tool
Rally, Version One, Mingle, ScrumPad, Target Process, Scrum Works, JIRA+GreenHopper,
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
7
Current tool adoption
No Tool
Spread sheet
Traditional PM Tool 24%
Agile PM Tool 11%
30%
16%
Wiki, Bug Tracking, InHouse, Other
18%
Source: http://targetprocess.com/LearnAgile/Whitepapers/AgileTools.aspx
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
8
Factors influencing tool choice
Location Co-location, distributed,
Project Size Single team, multiple teams
Process XP, Scrum, Kanaban
Customization Workflow, roles, data, reporting
Price Subscription-based, Perpetual, Site, By user, By project, A combination of user, project, storage, bandwidth etc,
Hosting Hosted shared, hosted private, on-site
Other usability, API, integration with other tools, social networking, customer support
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
9
Simple Agile PM Tool
Pros
1. Flexible, can be easily changed
2. Easy to use and understand
Cons
3. Tangible, perfect complement for reach face-to-face interaction
4. Great visibility to teams
Whiteboard/Corkboard, Card/Sticky, Marker, Flip Charts
1. Does not scale- large backlog, large project, large company
2. Does not work for distributed teams
3. Lack of reporting
5. Vulnerable to data loss, No Back up
5. Inexpensive
4. Limited visibility to Stakeholders
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
10
Spreadsheet as a PM Tool
Pros
Cons
Excel, or Google Spreadsheet
1. Easy to learn and use
2. Web-based spread (i.e. Google) sheets can be used by distributed teams
3. Inexpensive
1. Does not scale- large backlog, large project, large company
2. Reporting is possible but very cumbersome
3. Limited visibility to both team and stakeholders
4. Venerable to Data Loss
4. Back up exists
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
11
Agile PM Tool
Pros
Cons
Rally, Version One, Mingle, ScrumPad, Target Process, Scrum Works
1. Easy to scale
2. Appropriate for distributed teams
4. Provides change histories
1. Limited flexibility
2. Learning curve
3. Could be expensive
3. Insightful automated reporting
5. Protect from unauthorized data access and loss
4. Team needs to be logged in always for visibility
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
12
Concerns about using software tools for PM?
Teams are constrained by the tool’s capability
Teams following Agile process poorly might turn to tools for successful adoption
Tools might turn collaboration into reporting
Tools might replace the rich face-to-face interactions
Repurposed Agile tool might keep the pre-Agile practices
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
13
Agile PM Tools
Are Not:
-Replacements for direct communication/interaction
-Proxies for adoption of Agile values in the organization
-For helping teams become self-organized/self-managed
Are:
- For augmenting the productivity of the team
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
Conceptual architecture of an Agile PM tool
Let’s Try to Understand How an Agile Tool Should Looks at Agile PM
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
Unit of Work
storyBacklog
Macro View Micro View
What do we really manage on an Agile project?
rolls up
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
The context for managing a project
story
tasks
messages
impediments
filesbugs
comments
decisions
rules
time
Glossary
tags
Backlog
organization
collaboration
rating
reputation
wiki
Test cases
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
Right tool for the right audience
IDEPM Tool
• Community view of a project
• Management focus
• Generates macro level trend & insights for broader audience
• Suitable for integration with accounting/billing, CRM, ERP etc.
• Developer/Technical view of a project
• Engineering focus
• Pushes story/task level data to rest of the project team through PM tool
• Suitable for integration with code repository, build tool, test tool
What tool(s) is the most important for a software project team?
Svn/Git
CruiseControl
Load Runner
Ncover/Rcover
Getsatisfaction/UserVoice
Freshbook/Quickbooks
ZenDesk/Lighthouse
Stories and tasks
status and outcomes
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
How tools are evolving?
Traditional PM tools
Agile PM Tools
re-branding
purpose-built
Agile Application
LifecycleTools
re-branding
Be –aware of these tools
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
A simple Agile PM Tool selection decision tree
Single co-located team?
What Agile PM Tool?
New to Agile?
yes
New to Agile?
Single distributed team?
Start with simple toolStart with a hosted
Agile PM tool(e.g., ScrumPad)
yes no
yes
no
Start with a Google spreadsheet
yesGrow into
no
no
Grow into
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
20
ScrumaPad Demo
www.Code71.com www.ScrumPad.comCopyright 2010, Code71, Inc.
21
Q&A
“Right tools help teams do things faster, better”
Please contact for a ScrumPad
Demo:
Contact: srayhan@code71.comBlog: http://blog.syedrayhan.comCompany: http://www.code71.comProduct: http://www.scrumpad.com