Current and Future of Agile PM Tools Syed Rayhan, Nimat Haque Co-founders, Code71, Inc. Product:   http://www.scrumpad.com
Syed Rayhan’s Background Expertise Career <ul><li>Iterative incremental development </li></ul><ul><li>Technology planning ...
Nimat Haque’s Background Expertise Career <ul><li>Project Management </li></ul><ul><li>On-shore/Off-shore  software develo...
The tool questions? <ul><li>What features should an Agile PM tool have?  </li></ul><ul><li>What kind of tool is good for m...
What do we expect from a tool? Story/Bug/Task tracking Burndown charts Estimation tracking Product Backlog Management Mini...
Available options for tools Simple Tool Whiteboard + Corkboard + Card + Flip charts +Marker Spread sheet Excel with agile ...
Current tool adoption  No Tool Spread sheet Traditional PM Tool 24% Agile PM Tool 11% 30% 16% Wiki, Bug Tracking, InHouse,...
Factors influencing tool choice Location Co-location, distributed,  Project Size Single team, multiple teams  Process XP, ...
Simple Agile PM Tool Pros 1. Flexible, can be easily changed 2. Easy to use and understand Cons 3. Tangible, perfect compl...
Spreadsheet as a PM Tool Pros Cons Excel, or Google Spreadsheet 1. Easy to learn and use 2. Web-based spread (i.e. Google)...
Agile PM Tool Pros Cons Rally, Version One, Mingle,  ScrumPad , Target Process, Scrum Works 1. Easy to scale  2. Appropria...
Concerns about using software tools for PM? Teams are constrained by the tool’s capability Teams following Agile process p...
Agile PM Tools <ul><li>Are Not: </li></ul><ul><li>Replacements for direct communication/interaction </li></ul><ul><li>Prox...
Conceptual architecture of an Agile PM tool Let’s Try to Understand How an Agile Tool Should Looks at Agile PM
Unit of Work story Backlog Macro View Micro View What do we really manage on an Agile project? rolls up
The context for managing a project story tasks messages impediments files bugs comments decisions rules time Glossary tags...
Right tool for the right audience IDE PM Tool <ul><li>Community view of a project </li></ul><ul><li>Management focus </li>...
How tools are evolving? Traditional  PM tools Agile PM  Tools re-branding purpose-built Agile  Application  Lifecycle Tool...
A simple Agile PM Tool selection decision tree What Agile PM Tool? yes New to Agile? yes no yes no yes Grow into no no Gro...
ScrumaPad Demo
Q&A “ Right tools help teams do things faster, better” Please contact for a ScrumPad Demo: Contact:   [email_address] Blog...
Upcoming SlideShare
Loading in...5
×

Agile pm tool

4,079

Published on

A look at why use software tools to manage Agile projects, what to consider when selecting a tool, what to expect from the available tools in the market, and when to go for a tool. It also includes a simple decision tree for selecting a tool.

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,079
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
87
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Here are a list of questions we all have about Agile PM tools.
  • Atlassian GreenHopper=&gt; planning view, task board, chart board, card view, search view to JIRA – a issue tracking system (like Bugzilla)
  • Atlassian GreenHopper=&gt; planning view, task board, chart board, card view, search view to JIRA – a issue tracking system (like Bugzilla)
  • While most vendors claim to support all types of Agile processes, the reality is Scrum and Kanaban are different enough that a tool cannot do justice to both at the same time. Scrum and Kanaban use different control and tracking mechanisms. A tool that attempts to support both, can become confusing. ScrumPad supports Scrum.
  • SpreadsheettTemplates are available to help get started.
  • Be mindful of the concerns around using a software tool.
  • Choose to use a software tool for the right reasons.
  • 21/07/0806/29/08 An understanding of conceptual underpinnings of managing an Agile project might help with what to expect from a tool.
  • 21/07/0806/29/08 What do we really manage on an agile project? Scope. Scope is the only variable. We fix schedule through time-boxing, and resources by choosing a team size up-front. Story is the smallest unit of work that we plan and manage. Backlog is the roll-up view of stories. – release, product, or project level view
  • 21/07/0806/29/08 Story is at the center of the universe. Goal is to implement a story. Everything else provides a context to the execution of the story.
  • 21/07/0806/29/08 There two critical tools that any project team should have- PM tool and IDE. Each has its unique role on the project. They complement each other. There is a tendency to integrate with all kinds of tools and push all kinds of data to PM tool, which could clutter the view and become counter productive. Important to keep a clear separation between these two tools.
  • 21/07/0806/29/08 AALM – Extends beyond development, includes customer feedback to drive what to build before development, and customer problems (issues/bugs) during maintenance.
  • 21/07/0806/29/08 Be aware of selecting on-premise solution. Going with a on-premise solution will cost more and will be difficult to switch if the tool turns out to be not a right fit.
  • Tool should not get in the way Tool should complement
  • Tool should not get in the way Tool should complement
  • Agile pm tool

    1. 1. Current and Future of Agile PM Tools Syed Rayhan, Nimat Haque Co-founders, Code71, Inc. Product: http://www.scrumpad.com
    2. 2. Syed Rayhan’s Background Expertise Career <ul><li>Iterative incremental development </li></ul><ul><li>Technology planning and architecture </li></ul><ul><li>On-shore/Off-shore software development using Agile/Scrum </li></ul>Interests <ul><li>Co-founder, Code71, Inc. </li></ul><ul><li>14+ years of total experience </li></ul><ul><li>Co-author of “Enterprise Java with UML” </li></ul><ul><li>Cultural aspect of self-organizing team </li></ul><ul><li>Scrum for projects delivered remotely </li></ul><ul><li>Agile engineering practices </li></ul>
    3. 3. Nimat Haque’s Background Expertise Career <ul><li>Project Management </li></ul><ul><li>On-shore/Off-shore software development using Agile/Scrum </li></ul>Interests <ul><li>Co-founder, Code71, Inc. </li></ul><ul><li>Current job: Scrum Master at INPUT in Reston, VA </li></ul><ul><li>10+ years of total experience </li></ul><ul><li>Lean Software Engineering – Learning about Kanban </li></ul><ul><li>Coaching </li></ul><ul><li>Distributed Teams – how to get best out of remote teams </li></ul>
    4. 4. The tool questions? <ul><li>What features should an Agile PM tool have? </li></ul><ul><li>What kind of tool is good for my team? </li></ul><ul><li>What options are available? </li></ul><ul><li>Is a tool necessary for Agile adoption? </li></ul><ul><li>When is a simple whiteboard+card+marker good for team? </li></ul><ul><li>When is spreadsheet good for a team? </li></ul><ul><li>Do I need a tool? </li></ul><ul><li>What is the future trend for Agile PM tools? </li></ul><ul><li>Can I adopt traditional tool for Agile projects? </li></ul>
    5. 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
    6. 6. Available options for tools Simple Tool Whiteboard + Corkboard + Card + Flip charts +Marker Spread sheet Excel with agile templates Traditional PM Tool MS Project +MS Project Server, TFS, Clarity, Basecamp Agile PM Tool Rally, Version One, Mingle, ScrumPad , Target Process, Scrum Works, JIRA+GreenHopper,
    7. 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
    8. 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
    9. 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
    10. 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
    11. 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
    12. 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
    13. 13. Agile PM Tools <ul><li>Are Not: </li></ul><ul><li>Replacements for direct communication/interaction </li></ul><ul><li>Proxies for adoption of Agile values in the organization </li></ul><ul><li>For helping teams become self-organized/self-managed </li></ul><ul><li>Are: </li></ul><ul><li>- For augmenting the productivity of the team </li></ul>
    14. 14. Conceptual architecture of an Agile PM tool Let’s Try to Understand How an Agile Tool Should Looks at Agile PM
    15. 15. Unit of Work story Backlog Macro View Micro View What do we really manage on an Agile project? rolls up
    16. 16. The context for managing a project story tasks messages impediments files bugs comments decisions rules time Glossary tags Backlog organization collaboration rating reputation wiki Test cases
    17. 17. Right tool for the right audience IDE PM Tool <ul><li>Community view of a project </li></ul><ul><li>Management focus </li></ul><ul><li>Generates macro level trend & insights for broader audience </li></ul><ul><li>Suitable for integration with accounting/billing, CRM, ERP etc. </li></ul><ul><li>Developer/Technical view of a project </li></ul><ul><li>Engineering focus </li></ul><ul><li>Pushes story/task level data to rest of the project team through PM tool </li></ul><ul><li>Suitable for integration with code repository, build tool, test tool </li></ul>What tool(s) is the most important for a software project team? Svn/ Git Cruise Control Load Runner Ncover /Rcover Getsatisfaction/ UserVoice Freshbook/ Quickbooks ZenDesk/ Lighthouse Stories and tasks status and outcomes
    18. 18. How tools are evolving? Traditional PM tools Agile PM Tools re-branding purpose-built Agile Application Lifecycle Tools re-branding Be –aware of these tools
    19. 19. A simple Agile PM Tool selection decision tree What Agile PM Tool? yes New to Agile? yes no yes no yes Grow into no no Grow into Single co-located team? New to Agile? Single distributed team? Start with simple tool Start with a hosted Agile PM tool (e.g., ScrumPad ) Start with a Google spreadsheet
    20. 20. ScrumaPad Demo
    21. 21. Q&A “ Right tools help teams do things faster, better” Please contact for a ScrumPad Demo: Contact: [email_address] Blog: http://blog.syedrayhan.com Company: http://www.code71.com Product: http://www.scrumpad.com
    1. Gostou de algum slide específico?

      Recortar slides é uma maneira fácil de colecionar informações para acessar mais tarde.

    ×