1. CSCI 577b Tasks and Activities

2. Outline 577a to 577b Roles and Responsibilities
Preparation
Prototyping
Roles and Responsibilities
Old vs. New
Milestones and anchor points
Activities and Artifacts
11/3/2009

3. Preparing for 577b Analyze current situation
Team’s strengths and weaknesses
Project’s risks
Analyze current team’s competence and abilities
Who is continuing?
Missing roles and responsibilities
Roughly plan the activities
Not just the major milestones
11/3/2009

4. Preparing for 577b Define technologies to be used
Should already know by current phase
Develop functioning prototypes
Transition from throwaway
Use the specified technologies
Saves development effort in the future
Proof of concepts, not just GUI issues
11/3/2009

5. Outline 577a to 577b Roles and Responsibilities
Preparation
Prototyping
Roles and Responsibilities
Old vs. New
Milestones and anchor points
Activities and Artifacts
11/3/2009

6. Current Roles Architected Agile NDI/NCS Project Manager
Operational Concept Engineer
Prototyper
Requirements Engineer
NDI /NCS Acquirer
NDI / NCS Evaluator
Shaper
System Architect
UML Modeler
Life Cycle Planner
Life Cycler Planner
Feasibility Analyst
IIV&V
Quality Focal Point
11/3/2009

7. Prospective Roles Architected Agile NDI Intensive Project Manager
Operational Concept Engineer
Requirements Engineer
NDI /NCS Acquirer NDI / NCS Evaluator
System Architect
UML Modeler
Life Cycle Planner
Life Cycler Planner
Feasibility Analyst
Builder
Tester
Trainer
IIV&V
Quality Focal Point
11/3/2009

8. Builder Programmer Build system based on architecture design
Possibly DR/Intern students to fulfill role
Treated as part of the team
Require commitment
Should know the technologies well
11/3/2009

9. Tester Develop detailed acceptance test cases for system
Cover all core capabilities (at least)
Input
Expected outputs
Execute test cases
Record procedures and results
Develop regression test plan
What to test when modifying/upgrading the system
11/3/2009

10. Trainer Should know the system very well Train
Clients
Maintainer
Users
Training users may not be necessary depending on client’s needs
May train the client to train others
Training maintainer is critical
11/3/2009

11. Outline 577a to 577b Roles and Responsibilities
Preparation
Prototyping
Roles and Responsibilities
Old vs. New
Milestones and anchor points
Activities and Artifacts
11/3/2009

12. 11/3/2009

13. Rebaselined Foundations
Assess project status
Personnel
Skills and knowledge
Rebaseline prototypes
Re-prioritize requirements
Plan for 577b specifics
Construction and test plans
Transition strategies
Key risk items
Rebaselined Development Commitment Review (ARB)
11/3/2009

14. Construction Iteration #1
Start building the system
All core capabilities should be at least 80% complete
Developed and tested
Does not have to be perfect
Functioning capability should be present
Core Capability Drive-through
Hands on “drive-through” by the client
Verify capabilities and development progress
Comments and suggestions for improvements
11/3/2009

15. Construction Iteration #2
Finish up core capabilities
Developed and tested
The rest of 20%
Develop non-core capabilities (if time permits)
Prepare for transition
Transition and support plan
Regression test plan
User’s manual
Transition Readiness Review ARB
11/3/2009

16. Transition Execute transition plan Design-Code review
Install product
Provide training
Design-Code review
Operation Commitment Review
Project release
Client feedback
Hand over to client (acceptance)
11/3/2009

17. Questions?
11/3/2009