Description

This is the two-week period that begins the first Iteration of Release 1 Inception phase.  So coming out of that, we need to have a picture of the entire Release 1 architecture, subject to all the things we will learn during the Inception phase (and thereafter).

Required Before Starting

1. Input task lists (link downloads document) This will get revised during the two weeks
2. Existing requirements and open requests/suggestions from each IPT
3. Architecture development support tools in place:
   1. Confluence  - accounts (done?), organization (sufficient), best practices (must add a page to capture these - Action>JBG)
   2. Enterprise Architect - although Raytheon's contribution is not yet arranged, we'll look at using this tool directly for these documents
   3. Jira - Need to set up for use by teams (Action->JBG)
   4. EtherPad/GoogleDocs/other as needed
   5. OmniGraffle + Visio, and/or a drawing plug-in for Confluence
      1. best practice: upload original and png to Confluence
   6. Remote collaboration tools - as needed/decided by each team
   7. Team contact lists with roles, organization, and availability (leads can augment)
4. Expected resources availability to accomplish tasks (use existing lists in C.vii, plus estimated hires)

Intended Products

The primary focus is on the tasks and materials for the Inception period, but products and outcomes should allow for the entire Release 1 product where possible.

1. Updated tasks & subtasks lists (using good engineering judgment)
   1. Described
   2. Prioritized
   3. Estimated effort required/allocated
   4. Reviewed by Architecture Lead
2. Change and clarification requests for requirements documentation
3. Drawings and related artifacts labeled with acceptance/approval level
   1. Interaction roles, message types
   2. Updated (or new) UML diagrams representing component/service interactions
   3. Articulation of use cases/stress cases/usage scenarios AND/OR Sequence diagrams
4. Discussion/analysis/report documents in Confluence (import an archival copy from other collaboration tools as needed)
   1. Put temporary/provisional work in the relevant iteration for that subsystem
   2. Put 'mainline progress' in the main documents area for that subsystem
   3. Integrate progress into "the master document" (TBS) for the subsystem (process to be determined)
5. Tasks/action items/bugs in Jira, assigned and prioritized
6. Make sure the correct access/edit permissions exist on all the tools/repositories by all the participants
7. Technology integration list/assessment (update strawman list, reflect acceptance/approval)
8. Dependencies list (on other subsystems, in particular)

Proposed Process

Day.n indicates the day of the week in week n.

Most progress will be achieved by team members under the leadership of the IPT Lead. Team members may work together or independently, as appropriate to the tasks.

1. (Tue.1) Identify availability of team members (optionally, recruit more)
2. (Wed.1) Produce schedule of IPT meetings/activities for week, and deliver to Michael, John
3. (Wed.1) Complete outline of strategy for accomplishing goals
4. (Thu.1) Progress Assessment: IPT Leads and Architects (status, best practices, dependencies)
5. (Thu.1) Issues assessment (and promotion of major issues to management) complete
6. (Fri.1) Placeholder products in place
7. (Fri.1) Preliminary task lists and priorities complete
8. (Fri.1) Planned drawings and artifacts identified
9. (Mon.2) Progress Assessment: IPT Leads and Architects (status, best practices, dependencies)
10. (Tue.2) Task lists prioritized and estimated
11. (Tue.2) Drawings and related artifacts largely complete
12. (Tue.2) Technology integration and Dependencies lists complete
13. (Wed.2) All documentation on Confluence
14. (Wed.2) Task lists finalized
15. (Wed.2) Action items submitted