This spreadsheet presents consolidated views of the Agile Process to help project teams understand how to apply it. It includes a RASIC showing who leads and is involved in each activity, a RACI showing who owns and works on each work product, and a table showing when work products are worked on during the project. These views are recommendations and teams should do what is best for the project regardless of roles or responsibilities.

1. The AGILE Process RASIC Spreadsheet
This spreadsheet presents a number of consolidated views of the Agile Process to help project teams to
understand how to use and apply the Agile Process.
These views are present a set of recommendations aimed at helping project teams. They are just
recommendations and not hard and fast rules. You should always remember that the project team members
shoudl always be willing to role up their sleeves and do whatever is best for the team regardless of their job
title or where the RASIC allocates the responsibility.
The views included are:
1. An activity RASIC showing who leads and is involved in each activity.
2. A work product RACI that shows who owns and works on each work product
3. A work product evolution table that shows when the work products are worked on during the project.
Version 1.0 Final

2. SegmentReresentative
CompetencyCenterManager
ProgramManager
ITBusinessConsultant
ProgramArchitect
DeliveryManager
QAManager
ITProjectManager
ITConsultant
ITDesigner
ITTestManager
TestSupplier
Supplier
Lead Activity Key Phase
Business Establish Business Case Inception RA I C C C C C
Project Team Involve Stakeholders All RA R R C S R I I C
Project Team Achieve Acceptance Transition RA C C C R C I R I R S C
Prog Understand Mission Inception C C A S S R C C C
Prog Engage and Disengage Inception C C AR I I C I I I
Prog Launch Project Inception C A C C S C R S S S C C
Project Team Adapt Plans All C A I I R I R C C C C C
Project Team Agree Iterations All I I I I C I AR C C C C C
Project Team Guide Team All AR C C C
Project Team Coach Team All S S S S AR C C C S S
Project Team Evaluate Results All I I C C AR C C C S S
Project Team Handover Responsibilities Transition I I A C R S S S S S
Project Team Find Actors and Use Cases Inception C A C I R I I C
Project Team Select and Prioritize Use Cases All C C A I C I C R C C I C
Project Team Identify Architactural Requirements Elaboration C A I I I C R C I C
Project Team Specify Use-Case Modules Elaboration C I I I I I AR I C S I
Project Team Identify Tests Elaboration C C I I I AR S C
Project Team Set Up and Prepare Tests Elaboration I A R R
Project Team Identify Components Elaboration I C AR S
Project Team Realize Use Case Elaboration I C AR S
Project Team Determine Architecture Elaboration A R S
Supplier Define Components & Unit Tests Elaboration A R
Supplier Evolve Architectural Implementation Elaboration C C A R
Supplier Develop a Component Construction A R
Supplier Integrate System Construction I I I A I R
Supplier Build Test - System Test Construction I A R
Supplier Execute Test - System Test Construction I I A R
Supplier Prepare Product for Release Construction I I I S I A I R
Test Supplier Build Test - Integration / Chain Test Elaboration A R
Test Supplier Execute Test - Integtration / Chain Test Elaboration I I I I A R I
Project Team Evaluate Test All I I I I I I I I I AR S S
Project Team Support Deployment Transition C A S S S S R
Legend:
- R - Responsible - Those who are responsible for the
task, ensuring that it is done as per the approver.
- A - Accountable / Approver - Ultimately accountable
for the correct and thorough completion of the task (only
ever 1)
- S - Supports - Resources allocated to Responsible.
Unlike Consult, who may aid in the task, Support may
be tasked with work.
- I - Informed - Those who are kept up-to-date on
progress. One-way communication.
- C - Consulted - Those whose opinions are sought. Two-
way communication
Program Project Team

3. SegmentRepresentative
ProgramManager
ITBusinessConsultant
ProgramArchitect
DeliveryManager
QAManager
ITProjectManager
ITConsultant
ITDesigner
ITTestManager
TestSupplier
Supplier
Work Product
Business Case AR C C C C C I I I I
Stakeholder Analysis AR I C C I I C C I I I I
Feature List R I AR C I I I C I I I I
Glossary AR C C I I I R C I I I
Project Plan C R I I A I R C I C I I
Master Test Plan I I I I C A C I I R C C
Risk List C C C C C C AR C C C C C
Iteration Plan C I I I C I AR C C C C C
Iteration Assessment C I I I C I AR C C C C C
Use-Case Model AC I C C I I I R I I I I
Use-Case Specification AC I C I I I I R I I I I
Supplementary Requirements AC I C C I I I R R I I I
Function Point Analysis A C C
Reference Estimate I
Productivity Analysis I
Architectural Description I I A I I I I R I I C
Architectural Test Case I I C I I A R R
Test Case C C I I A R R
Use-Case Realization C AR I I I
Design Model C AR I C
Component Description A I R
Source Code A R
Unit Test A I R
Build A AR
Release Description I I I I I I C I A I R
Test Line Agreement I I I AR I
Test Specification - System Test I A I R
Test Results - System Test A I R
Test Specification - Integration / Chain A R I
Test Results - Integration / Chain A R I
Defect List I I I I I I I I I AR C C
Test Report I I I I I I I I I AR C C
Legend:
- R - Responsible - Those who are responsible for
the production of the work product, ensuring that it is
done as per the Accountable approver.
- A - Accountable / Approver - Ultimately
accountable for the correctness and completeness
of the work product (only ever 1)
- I - Informed / Uses - Those who use the work
product as inputs into their activities.
- C - Consulted / Contributes to - Those who are
consulted about or contribute to the creation and
update of the work product.
Program Project Team

4. Work Product Initiate Inception Elaboration Construction Transition MoSCoW Purpose
Business Case Create Final Maintained Maintained Maintained Could
The business case will need to be maintained if there
are any significant problems or delays during the
Transition Phase
Stakeholder Analysis Create Final Kept up to date Kept up to date Kept up to date Could
Clarifies the stakeholder involvement. May have to be
updated if there are any significant changes in the
stakeholder community
Feature List Create Final Kept up to date Kept up to date Kept up to date
Glossary Create Update Final Kept up to date Kept up to date Could
Will need to be updated if definitions change, new
terms are needed or clarification of terms is required.
Project Plan Recommended Create Final Kept up to date Kept up to date Could
The plan may need to be revised if there are significant
delays or other problems.
Master Test Plan Create Final Kept up to date Kept up to date Could
May need to be updated if new Test Risks appear
during the phase.
Risk List Create Update Update Update Final Must
Clarifies the Top 10 Risks and demonstrates that it is
OK to end the project.
Iteration Plan Recommended Create / Final Create / Final Create / Final Create / Final Should
Archived copies of the plans for the iterations
completed in the phase
Iteration Assessment Recommended Create / Final Create / Final Create / Final Create / Final Should
The iterations assessments for the iterations completed
in the phase
Use-Case Model Create Update Final Kept up to date Kept up to date Could
Will need to be updated if change requests lead to the
discovery of new actors or use cases.
Use-Case Specification Recommended Create Update Final Kept up to date Could
May need to be updated if change requests lead to late
changes to the requirements.
Supplementary Requirements Recommended Create Final Kept up to date Kept up to date Could
May need to be updated if change requests lead to late
changes to the requirements.
Architectural Description Create Update Final Kept up to date Kept up to date Could
May need to be updated if defects or change requests
lead to late changes to the architecture..
Function Point Analysis Create Update Update Final Must
Captures an estimated count of the implemented
functionality
Reference Estimate Recommended Recommended Recommended
Productivity Analysis Final Must
Captures the spent hours and gives a Product Delivery
Rate for the project
Architectural Test Case Recommended Create / Final Kept up to date Kept up to date Could
May need to be updated if defects or change requests
lead to late changes to the architecture..
Test Case Create Final Fixed Could
May need to be updated if change requests lead to late
changes to the requirements.
Use-Case Realization Recommended Recommended Create Final Fixed Could
May need to be updated if defects or change requests
lead to late changes to the system's dynamic design.
Design Model Recommended Create Update Final Fixed Could
May need to be updated if defects or change requests
lead to late changes to the system's static design.
Component Description Create Final Fixed Could
May need to be updated if the components described
have to be fixed or the interfaces refactored.
Source Code Recommended Create Final Fixed Must The source code for the releases.
Unit Test Create Final Fixed Must Developer tests for all components changed.
Build Recommended Create Final Fixed Must
Assembles the bug fix releases through out the phase
for thorough system and integration testing.
Release Description Create Update Final Must Describes the contents of each release produced.
Test Line Agreement Recommended Create Final Kept up to date Could
Poor quality may lead to an extension or increase in the
amount of testing required.
Test Specification - System Test Recommended Create Final Kept up to date Could
May need to be updated if change requests lead to late
changes to the requirements.
Test Results - System Test Recommended Create Update Final Must
Test results from the system testing of any releases
produced.
Test Specification - Integration / Chain Create Final Kept up to date Should
Test specifications for any chain or nearest neighbor
testing. Essential if the application being produced is
part of a chain.
Test Results - Integration / Chain Create Update Final Should Test results from the chain / integration testing
Defect List Recommended Create Update Final Must Captures any defects found
Test Report Recommended Create Update Final Must Summary of the results of the testing
Phase (Use the plus buttons above to expand)