Life Cycle Plan (LCP)
E-LockBox
Team 5
ID / Role / Name1 / Builder & Feasibility analyst / Azuka Okuleye
2 / Tester & Operational Concept Engineer / Huaiqi Wang
3 / Builder & Prototyper / Weiyi Zhong
4 / Builder & System Architect / Woon Kim
5 / Tester & Quality Focal Point / Cecilia Jou
6 / Builder & Project Manager & Life Cycle Planner / Chen Gui
02-07-2014
24
Table of Tables
Version History
Date / Author / Version / Changes made / Rationale /09/25/13 / Woon& Dejie Meng / 1.0 / First document of LCP / To fit CS577 course content
10/13/13 / Chen Gui / 1.0 / Second document of LCP and changed from first LCP / To fit Valuation Phase
10/20/13 / Chen Gui / 1.1 / Revise LCP after FCR ARB / To fix and revise mistakes after FCR ARB
11/23/13 / Chen Gui / 2.0 / Add Iteration plan overview / To create iteration for next semester.
11/28/13 / Chen Gui / 2.1 / Update first two parts of LCP / Update the LCP for next semester
12/1/13 / Chen Gui / 2.2 / Update all LCP / Update the LCP for next semester
12/4/13 / Chen Gui / 2.3 / Revise resource estimation part / Some assumptions has been changed
02/07/14 / Chen Gui / 3.0 / Update status of LCP and iteration plan / Since TCP had been changed, make them consistent.
02/17/14 / Chen Gui / 3.1 / Add CCD Preparation Plans / Make first version of CCD Preparation Plans
03/29/14 / Chen Gui / 4.0 / Add Iteration Assessment / Implement core capabilities and record results
Table of Contents
Life Cycle Plan (LCP) i
Version History ii
Table of Contents iii
Table of Tables iv
Table of Figures v
1. Introduction 1
1.1 Purpose of the LCP 1
1.2 Status of the LCP 1
1.3 Assumptions 1
2. Milestones and Products 2
2.1 Overall Strategy 2
2.2 Project Deliverables 4
3. Responsibilities 7
3.1 Responsibilities by Phase 7
3.2 Skills 10
4. Approach 14
4.1 Monitoring and Control 14
4.2 Methods, Tools and Facilities 15
5. Resources 16
6. Iteration Plan 22
6.1 Plan 22
6.1.1 Capabilities to be implemented 22
6.1.2 Capabilities to be tested 23
6.1.3 Capabilities not to be tested 23
6.1.4 CCD Preparation Plans 23
6.2 Iteration Assessment 24
6.2.1 Capabilities Implemented, Tested, and Results 24
6.2.2 Core Capabilities Drive-Through Results 25
6.3 Adherence to Plan 27
Table of Tables
Table 1: Artifacts Deliverables in Exploration Phase 4
Table 6: Construction iteration capabilities to be implemented 22
Table 7: Construction iteration capabilities to be tested 23
Table 8: Capabilities implemented, tested, and results 24
24
Table of Tables
Table of Figures
24
1. Introduction
1.1 Purpose of the LCP
The purpose of LCP is to improve development speed, quality and project tracking and control, client relation, to minimize overhead and risk exposure.
If we don’t set a plan, we will not know when to finish object. That will cause a delay on other part. So we need to a set of plan that we can follow for development speed. Also LCP would help to improve quality of the project because of the theory of ICSM. Since we follow the plan, we can track and control by reviewing the LCP. Also clients will be satisfied because they know what is going on and they can expect what they want on as planned.
One of the reasons that we write LCP is that it will minimize overhead and risk exposure because we will be able to see what would be risks so we could prevent that risks before it occur.
1.2 Status of the LCP
The status of the LCP is currently at Rebaseline Development Commitment Package version number 3.0. The major changes from Development Commitment Package version number 2.3 are:
1. Update iteration plan
1.3 Assumptions
Schedule: 12 weeks in 2013 fall, 12 weeks in 2014 spring, and 24 week in total
Personnel Resource: 7 people participate in project in 2013 fall and 6 of them will continue to take it in 2014 spring. 1 new teammate will join in team in the next semester.
2. Milestones and Products
2.1 Overall Strategy
The e-lockbox is following Architected Agile process because a majority of functions and service are unable to be met by other strategy, such as NDI-Intensive, Net-Centric Services. What’s more, we take use of process decision graph to make a final decision.
Figure 1
According to the graph, we can decide to use Architected Agile process because there is only one point left.
Exploration phase
Duration: 08/26/13 – 09/15/13
Concept: to know what the client wants and what would be the best tool to achieve the goal
Deliverables: VC Package
Milestone: Valuation Commitment Review
Strategy: First incremental Commitment Cycle
Valuation phase:
Duration: 09/16/13 – 10/16/13
Concept: have identified operational concepts, win conditions, architecture, feasibility evidences, and life-cycle plan. The phase has prioritized the win conditions, implemented the prototypes.
Deliverables: FC Package
Milestone: Foundation Commitment Review
Strategy: First incremental Commitment Cycle
Foundation phase:
Duration: 10/17/13 – 12/06/13
Concept: identified more clearly operational concepts, win agreements, architecture, feasibility evidences and life-cycle. The phase implements the prototype/ product demo, make acceptance test plan and cases.
Deliverables: DC Package
Milestone: Development Commitment Review
Strategy: First increment Commitment Cycle
Foundation Phase – Rebaseline:
Duration: 01/13/14 – 02/17/14
Concept: Since some teammates might leave and new teammates might come, the roles & responsibilities should be reallocated. In addition, after a winter break, teammate should spend time on accessing project status, preparing for development phase, and testing.
Deliverables: RDC Package
Milestone: Rebaselined Development Commitment Review
Strategy: Incremental Commitment Cycles (Architected-Agile)
Development Phase – Construction Iteration:
Duration: 02/17/14 – 04/14/14
Concept: Implement, test, quality assurance, contact with clients and write user guide.
Deliverables: IOC & TRR Package
Milestone: CCD & Transition Readiness Reviews
Strategy: Incremental Commitment Cycles (Architected-Agile)
Development Phase – Transition Iteration:
Duration: 04/14/14 – 04/28/14
Concept: install/ transit the system, train users, archive final product, release product and obtain client evaluation.
Deliverables: Final Product Archive
Milestone: Operational Commitment Review
Strategy: Incremental Commitment Cycles (Architected-Agile)
Operation Phase
Duration: 04/28/14 – 05/12/14
Concept: support clients, users and maintainers, and solve problems.
Deliverables: NA
Milestone: NA
Strategy: Incremental Commitment Cycles (Architected-Agile)
2.2 Project Deliverables
2.2.1 Exploration Phase
Table 1: Artifacts Deliverables in Exploration Phase
Artifact / Due date / Format / MediumClient Interaction Report / 9/20/2013 / .doc, .pdf / Soft copy
Valuation Commitment Package
· Operational Concept Description (OCD) V1.0
· Life Cycle Plan (LCP) V1.0
· Feasibility Evidence Description (FED) V1.0 / 09/27/2013 / .doc, .pdf / Soft copy
Project Plan / Bi-Weekly Monday / .mpp / Soft copy
Progress Report / Bi-Weekly Monday / .xls / Soft copy
2.2.2 Valuation Phase
Table 2: Artifact Deliverables in Valuation Phase
Artifact / Due date / Format / MediumFoundation Commitment Package
· Operational Concept Description (OCD) F1.1
· Life Cycle Plan (LCP) F1.1
· Feasibility Evidence Description (FED) F1.1
· Prototype Repost(PRO) F1.1
· System and Software Architect Description(SSAD) F1.1 / 10/23/2013 / .doc, .pdf / Soft copy
Project Effort / Every Monday / Text / ER system
Project Plan / Bi-Weekly Monday / .mpp / Soft copy
Progress Report / Bi-Weekly Monday / .xls / Soft copy
2.2.3 Foundations Phase
Table 3: Artifact deliverable in Foundations Phase
Artifact / Due date / Format / MediumDevelopment Commitment Package
· Operational Concept Description (OCD) D1.0
· Life Cycle Plan (LCP) D1.0
· Feasibility Evidence Description (FED) D1.0
· Test Plan and Cases D1.0
· System and Software Architect Description(SSAD) D1.0 / 12/09/2013 / .doc, .pdf / Soft copy
Project Effort / Every Monday / Text / ER system
Project Plan / Bi-Weekly Monday / .mpp / Soft copy
Progress Report / Bi-Weekly Monday / .xls / Soft copy
2.2.4 Foundation Phase - Rebaseline
Table 4: Artifact deliverable in Foundations Phase - Rebaseline
Artifact / Due date / Format / MediumRebaselined Development Commitment Package
· Operational Concept Description (OCD) RD1.0
· Life Cycle Plan (LCP) RD1.0
· Feasibility Evidence Description (FED) RD1.0
· Test Plan and Cases(TPC) RD1.0
· System and Software Architect Description(SSAD) RD1.0
· Support Initial Description (SID) RD 1.0
· Transition Plan (TP) RD 1.0 / 02/17/2014 / .doc, .pdf / Soft copy
Project Effort / Every Monday / Text / ER system
Project Plan / Bi-Weekly Monday / .mpp / Soft copy
Progress Report / Bi-Weekly Monday / .xls / Soft copy
2.2.5 Development Phase – Construction Iteration
Table 5: Artifact deliverable in Development Phase – Construction Iteration
Artifact / Due date / Format / MediumIOC Package
· Operational Concept Description (OCD) IO1.0
· Life Cycle Plan (LCP) IO1.0
· Feasibility Evidence Description (FED) IO1.0
· Test Plan and Cases(TPC) IO1.0
· System and Software Architect Description(SSAD) IO1.0
· Support Initial Description (SID) IO 1.0
· Transition Plan (TP) IO 1.0 / 03/26/2014 / .doc, .pdf / Soft copy
TRR Package
· Operational Concept Description (OCD) TR1.0
· Life Cycle Plan (LCP) TR1.0
· Feasibility Evidence Description (FED) TR1.0
· Test Plan and Cases(TPC) TR1.0
· System and Software Architect Description(SSAD) TR1.0
· Support Initial Description (SID) TR 1.0
· Transition Plan (TP) TR 1.0 / 04/14/2014 / .doc, .pdf / Soft copy
User Guide V1.0 / 03/31/2014 / .doc, .pdf / Soft copy
Project Effort / Every Monday / Text / ER system
Project Plan / Bi-Weekly Monday / .mpp / Soft copy
Progress Report / Bi-Weekly Monday / .xls / Soft copy
2.2.6 Development Phase – Transition Iteration
Table 6: Artifact deliverable in Development Phase – Transition Iteration
Artifact / Due date / Format / MediumUser Guide V2.0 / 04/28/2014 / .doc, .pdf / Soft copy
Product Archive / 04/28/2014 / .doc, .pdf / Soft copy
Project Effort / Every Monday / Text / ER system
Project Plan / Bi-Weekly Monday / .mpp / Soft copy
Progress Report / Bi-Weekly Monday / .xls / Soft copy
2.2.7 Operation Phase
Table 7: Artifact deliverable in Operation Phase
Artifact / Due date / Format / Medium· NA / NA / .doc, .pdf / Soft copy
3. Responsibilities
3.1 Responsibilities by Phase
Table 4: Stakeholder's Responsibilities in each phase
Team Member / Role / Primary / Secondary ResponsibilityExploration / Valuation / Foundation / Foundation - Rebaseline / Development- Construction Iteration / Development- Transition Iteration
Name: Living Advantage
Role: Client Maintainer / Primary Responsibility
1. provide with requirements, winwin conditions, and prioritize them
2. provide with access to current system
3. interact with developers and give feedback
4. attend winwin sessions / Primary Responsibility
1. provide with more specific , detailed requirements, and help capture operational concepts
2.offer feedback for prototype 3.interact with developers
4.attend FCR ARB / Primary Responsibility
1.provide with feedback for requirements specification, and achieve winwin agreement
2.offer feedback for prototype and test cases
3. interact with developers / Primary Responsibility
1.assess rebaseline prototype
2.interact with developers / Primary Responsibility
1. provide with feedback for developing system
2. offer more test cases
3. interact with developers
Secondary Responsibility
1.invite foster youth(client) to test the system and acquire training / Primary Responsibility
1.test the system
2.give feedback 3.interact with developers
4.acruire training
5. acquire information and documents to maintain the system
Secondary Responsibility
1.invite foster youth(client) to test the system and acquire training
Name:
Cecilia Jou
Role:
II V&V & Primary Quality Focal Point / Primary Responsibility
1.Verify and Validate Work Products with Bugzilla
2.Monitor the process in Bugzilla
3. Defect Identification / Primary Responsibility
1.Verify and Validate Work Products with Bugzilla
2.Monitor the process in Bugzilla
3. Identify Quality Management Strategy
4. Defect Identification / Primary Responsibility
1.Verify and Validate Work Products with Bugzilla
2.Monitor the process in Bugzilla
3. Quality Management
4. Defect Identification / Primary Responsibility
1.Verify and Validate Work Products with Bugzilla
2.Monitor the process in Bugzilla
3. Quality Management
4. Record technical debt, metrics / Primary Responsibility
1.Verify and Validate Work Products with Bugzilla
2.Monitor the process in Bugzilla
3. Defect Identification
4. Identify Test Plan / Primary Responsibility
1.Verify and Validate Work Products with Bugzilla
2.Monitor the process in Bugzilla
3. Defect Identification
Name:
Chen Gui
Role:
Project Manager, & Life Cycle Planer / Primary Responsibility
1.Make Project Plan
2.Record Project Progress
3.Organize Meetings with Teammates and Clients
4. Identify Milestones and Products
5.Identify Responsibilities and Skills
6. Interact with clients / Primary Responsibility
1.Make Project Plan
2.Record Project Progress
3.Organize Meetings, ARB with Teammates and Clients
4.Identify Life Cycle Strategy
5.Identify Milestones and Products
6.Identify Responsibilities and Skills
7.Estimate Project Effort and Schedule
8.Identify Life Cycle Management Approach
9. Interact with clients / Primary Responsibility
1.Make Project Plan
2.Record Project Progress
3.Organize Meetings, ARB with Teammates and Clients
4. Assess Life Cycle Content
5.Make Iteration Plan / Primary Responsibility
1.Recrut new teammates
2. Make project Plan
3.Record Project Progress
4.Organize Meetings, ARB with Teammates and Clients
5. Assess Life Cycle Content / Primary Responsibility
1.Make Project Plan
2.Record Project Progress
3.Organize Meetings, ARB with Teammates and Clients
4.develop the system / Primary Responsibility
1.Make Project Plan
2.Record Project Progress
3.Organize Meetings, ARB with Teammates and Clients
4. develop and improve the system
5.train users
Name:
Qiutong Song(13 fall)
Huaiqi Wang(14 spring)
Role:
Operational Concept Engineer / Primary Responsibility
1.Identify Operational Concepts
2.Explore Current System
3.Record Client interaction
4. Interact with clients / Primary Responsibility
1. Identify Objectives, Constraints and Priorities
2.Identify Organizational and Operational Transformation
3.Identify Shared Vision
4.Identify new Operational Concepts
5. Continue to explore Current System and Communicate with users.
6. Interact with clients / Primary Responsibility
1.Assess Operational Concept
2.Help other teammates to understand Operational Concepts better / Primary Responsibility
1.study the project and system
2.improve OCD
3.verify and validate the artifacts / Primary Responsibility
1.Develop the system
2.Test the system / Primary Responsibility
1. Develop the system
2.Test the system
Name:
Dejie Meng
Role:
Requirement Engineer& Secondary Quality Focal Point / Primary Responsibility
1.Acquire winwin conditions and manage winbook
2. Help identify new operational concepts
3.Interact with clients
Secondary Responsibility
1.Help Primary Quality Focal Point to identify defect / Primary Responsibility
1.Summarize, prioritize, analyze winwin conditions
2. Help identify new operational concepts
3. Help establish proposed system
4. Interact with clients
Secondary Responsibility
1. Help Primary Quality Focal Point to identify defect / Primary Responsibility
1.Access requirement definition
2.Achieve WinWin Agreement with clients
3.Help complete architecture
Secondary Responsibility
1. Help Primary Quality Focal Point to identify defect / Primary Responsibility
1.develop rebaseline architecture
2. Help new teammate to study the project and system
Secondary Responsibility
1. Help Primary Quality Focal Point to identify defect / Primary Responsibility
1. Identify Test Plan
2. Develop the system
Secondary Responsibility
1. Help Primary Quality Focal Point to identify defect / Primary Responsibility
1. Help Primary Quality Focal Point to identify defect
2. Write user guide and train users
Name:
Weiyi Zhong
Role:
Prototyper / Primary Responsibility
1. Help Operational Concept Engineer identify operational concepts.
2.Interact with clients / Primary Responsibility
1. Assess Prototype and Components
2. Analyze and Prioritize Capabilities to Prototype
3.Develop Prototype
4. Establish New Operational Concept
5. Prepare development / production environment
6. Interact with clients
7. Record the process for prototype / Primary Responsibility
1. Assess Prototype and Components
2. Analyze and Prioritize Capabilities to Prototype
3.Develop Prototype
4.Record the process for prototype
5. Prepare development / production environment / Primary Responsibility
1.Develop rebaseline prototype
2.prepare for the development phase / Primary Responsibility
1. Develop the system
1. Test Procedures and Results
2.Identify Test Plan
3.Identify Test Procedures
4.Perform Testing
5.Record Test Results / Primary Responsibility
1.Perform Testing
2.Record Test Results
Name:
Woon kim
Role:
System Architect / Primary Responsibility
1. Help Operational Concept Engineer identify operational concepts.
2.Interact with clients / Primary Responsibility
1.Analyze the Proposed System
2. Make UML Model
3. Define Technology-Independent Architecture / Primary Responsibility
1. Specify Architecture Styles, Patterns and Frameworks
3. Assess System Architecture
4. Make UML Model
5. Define Technology-Dependent Architecture / Primary Responsibility
1.Develop rebaseline architecture
2. prepare for the development phase / Primary Responsibility
1.Develop the system
2.Test the system / Primary Responsibility
1.Develop the system
2.Test the system
Name:
Azuka Okuleye
Role:
Feasibility analyst / Primary Responsibility
1.Identify risks and Assess and Plans to Mitigate Risks
2.Interact with clients / Primary Responsibility
1.Analyze Business Case
2. Identify risks and Assess and Plans to Mitigate Risks
3. NDI/NCS Interoperability Analysis
/ Primary Responsibility
1. Identify risks and Assess and Plans to Mitigate Risks
2. Assess Feasibility Evidence / Primary Responsibility
1.Revise FED
2. prepare for the development phase
3.Help finish rebaseline protytype / Primary Responsibility
1.Develop the system
2.Test the system / Primary Responsibility
1.Develop the system
2.Training Clients
3.Deploy the system
Name:
Foster youth
Role:
Clients of Living advantage / NA / NA / NA / NA / Primary Responsibility
1.Accept training 2.Test the system and give the feedback. / Primary Responsibility
1.Accept training 2.Test the system and give the feedback.
3.2 Skills
Table 5: The skills needed for each role