Project Management

Agile Tooling

last edited by: Antonio Villarruel on Mar 25, 2022 10:17 AM login/register to edit this page
Keywords: Knowledge and Skills PMI-ACP Tools and Techniques

1 Overview
2 Importance
3 PMI-ACP Exam Outline Reference
4 Body
5 History
6 Current practice
7 Sources & Reference
8 External Links

Community Guide of the PMI-ACP Boosting Team Performance Practices


The Agile Manifesto, as it spells out the principals of agile development, does not necessarily endorse tools. It values individuals and interactions over processes and tools. The premise here is that right individuals, interacting well, will find or create whatever processes and tools that will serve them best; the best processes and tools, on the other hand, can't bring effectiveness to individuals interacting poorly.


Appropriate tools can increase productivity, innovation and collaboration between team members and should be chosen carefully.

PMI-ACP Exam Outline Reference

Tools and Techniques Communication


Agile development places a premium on simplicity. The philosophy extends to the type of tools agile developers recommend - index cards, pens, and white boards.

The primary activities of agile software development are straightforward - developers must build software, track its progress, and test what they have built. Tools that aid developers with these core tasks are recommended:
  • Robust IDEs/Editors/Development tools
  • Good code managers that support frequent check-ins and versions
  • Code analysis tools for fast error analysis
  • Refactoring tools that help make code more readable, maintainable, and extensible
  • Automated build systems to keep the code integrated all the time
  • Testing tools that support both unit testing and automated testing.

  • In recent years, tools have evolved to better support Agile efforts, among these are several that support a new type of project management - Agile Project Management (APM) or Agile Application Lifecycle Management (AALM). Agile-focused tools understand the Agile cycle and help with planning, collaboration, communication, reporting, etc.

    Tools in an agile context are not focussed on or chosen for their compatability with a predefined process. Instead, tools should adapt to your needs and should assist you in improvements to your SDLC processes:
  • Management
  • Development
  • Testing
  • Validation
    Tools should not drive these processes instead people and value stream should. Some popular low-tech tools are:
    Transparency and Collaboration Tools:
  • WIKIs
  • White boards
  • Task / Kanban boards
  • Team Space that promotes Osmotic Communications

    Some popular hi-tech tools are:
    Project Management Tools:
  • Mingle
  • Jazz
  • VersionOne
  • Rally
  • TargetProcess
  • SEER

    Continuous Delivery Tools
  • Go
  • Bitbucket

    Automated Testing Tools
  • Twist
  • Vansah


    Current practice

    Sources & Reference

    Manifesto for Agile Software Development
    Highsmith, Jim. (2009). Agile Project Management: Creating Innovative Products. Addison-Wesley Professional. ISBN-10: 0321658396. ISBN-13: 978-0321658395
    Agile ALM: Redefining ALM with Five Key Practices

    External Links

    Project Management Tools:
  • Mingle
  • Jazz
  • VersionOne
  • Rally
  • TargetProcess
  • Trello
  • SEER

    Some lists of free tool reviews and collections:
  • Mountain Goat Software
  • 10 Free Scrum Tools
  • 10 Free Scrum PM Tools
  • Open Source Scrum

    Continuous Delivery Tools

  • Go

    Automated Testing Tools
  • Twist

  • last edited by: Antonio Villarruel on Mar 25, 2022 10:17 AM login/register to edit this page

    Comments (1)

    Login/join to subscribe

    It is wonderful to be here in the great state of Chicago.

    - Dan Quayle