Benefits:    Limitations:  
1. History

2. Example

3. References

4. External links

This page was an abandoned draft that has now been declined or rejected as duplicating an existing article. Any details in this draft that are not in the article may be added to the article. This draft should be allowed to be deleted six months after this date. Robert McClenon (talk) 05:49, 20 January 2019 (UTC)}}

A Project Anatomy (also Integration Anatomy or Organic Integration Plan ) is a tool for integration planning that visualizes dependencies between work items in development projects. It is mainly used in integration driven development projects.

The Project Anatomy has evolved from the System Anatomy and in its purest form the work items (called Work Packages) reflect the development of system capabilities. Often a more pragmatic approach is taken, though, where work packages may contain other items with important dependencies as well, e.g. HW Deliveries for embedded systems.

Benefits:

• Simple
• Easy to grasp view of what to do, what is done and the dependencies between work packages
• Collaborative
• Common view for developers, project managers and sponsors
• Helps in finding and managing risks and delays
• Can be used to manage dependencies between teams and sprints in large agile projects

Limitations:

• Can include, but not manage, lead time aspects
• Can include, but not manage, resource aspects

History

History of System Anatomies

Project Anatomies have evolved from System Anatomies, mainly at Ericsson, since the late 1990’s. Both the terminology and the methodology have differed between organizations and the difference between system anatomy, project anatomy, delta anatomy and integration anatomy is sometimes diffuse or non-existent. In 2004 FindOut Technologies presented a SW tool (Paipe) for managing anatomies with more properties. The company has, since then, worked to establish the term Project Anatomy.

Example

The Project Anatomy below is an example showing the work packages needed to develop a simple issue management system.

Work packages with many dependencies are called spiders and indicate a risk. The risk may be managed by splitting the work package or by moving dependants of it to later shipments (increments).

The colors indicate the current status of work packages, where green means “on track”, yellow means “at risk” and red means “off track”. Blue work packages are done.

References

Lars Taxén (ED), The System Anatomy, Studentlitteratur, ISBN 978914407074 (not yet published)

External links

• Paipe (SW tool for Anatomies) FindOut Technologies