Project FSW Status

1
ltProjectgt FSW Status

• Month/Year
• Preparer(s)

FSB Status Reporting Template, Version 2.1 April
2005 Companion template is FSB_Status_Spreadsheet
_V2 The updated FSW Status Report template will
be baselined at the April 2005 FSB Standards CCB
Mtg. (4/25/05) Changes are anticipated as use of
the templates occurs.
2

• Continuing issues associated with this template
• Schedule
• Timeline tool -- use Project if thats best for
  you but try to make it readable and include
  mission milestones
• How to deal with replans for now include last
  schedule and new schedule in package following
  replans
• FSW Risks
• FSB Tool output format enter risks now
• Staff Plan vs Actuals spreadsheet format
• How to deal with replans
• FSW Development and Test Metrics
• Presumably some metrics presentation from ReqPro
  and MKS will be common
• FSW Process Monitoring Metrics (for CMMI)
• Stakeholder Involvement
• Data Management
• ...

3
ltProjectgt FSW Status Summary
Insert one FSW Team Fever Chart from
FSB_Status_Spreadsheet_V2.xls Customize for
number of flight CPU.
4
ltProjectgt FSW Significant Events Log
Insert FSW Team Events Log from
FSB_Status_Spreadsheet_V2.xls This is intended
to be a Scrolling-type log of significant
happenings that would be useful as reference.
E.g., Changes in Project requirements, schedules,
funds, personnel External dependency issues
Changes in FSW staff or assignments New
requirements. Some significant events justify a
new FSW schedule, staffing or cost plan. When
this happens the event causing the replan and the
replan date (reference) are to be provided.
5
FSW Systems Engineering Activities
This is intended as FSW systems engineering
activities typically supported by the PDL, DTL
and TTL (and others on the PDT). Include trades,
issues w/ external organizations, operations
concept influence, simulator deficiencies, etc.
The Lead Engineer is the person (often not part
of the PDL) responsible for coordinating the
activity to completion (e.g., FSW Sys. Manager,
Mission Sys. Engr., FOT, )
6
FSW Schedule Overview Rev. Nbr. n, xx/xx/xx

• Each schedule update must be identified with
  Revision Number, must be dated and must include
  reason for update.
• Multi-year FSW schedule graphic that is readable
  -- this year and future years thru Launch
• Project milestones (minimally major reviews, IT
  start, CPTs, ship, launch)
• FSW Team milestones
• FSW Team Formal Reviews -- SRR, PDR, CDR, STRR,
  ATR
• FSW Requirements (prelim, baselined), ICDs (show
  each with baseline milestones)
• FSW Product Plan (prelim, baselined)
• FSW Test Plan (prelim, baselined)
• FSW CM Plan (prelim, baselined)
• FSW Tools (ReqPro, CM, DCR) (PRs, tools received,
  system set-up and full use)
• FSW Testbed Milestones
• FSW Delivery milestones to internal groups (e.g.
  ACS to CDH for build delivery)
• FSW Delivery milestones to external groups
• for each build design, code-UT, Integration
  test
• for each build test preparations, build test
• FSW System Test test preparations, system
  test, AT
• Show progress each month.

Tool for schedule TBR. If Microsoft Project,
try removing date columns to create readability.
This is intended to be a high level FSW schedule
in the context of mission milestones and testbed
deliveries.
7
FSW Risks Update

• Enter Risks into FSB Risk Management tool at
  FSW.gsfc.nasa.gov/internal/rm/
• Extract TBR element from tool and paste onto
  chart.
• Include known and potential risks to the FSW team
  product quality, schedule, cost, etc.

Risks written __ Risks Open __ Risks retired
this month __ New risks added this month __
High severity 0, Medium severity 3, Low
severity 2 Risks modified this month __ High
severity 0, Medium severity 2, Low
severity 1
8
FSW Documents Status
Insert FSW Team Documents Status from
FSB_Status_Spreadsheet_V2.xls This chart will
be usable for SRR, PDR, CDR
9
FSW Receivables Status
Insert FSW Team Receivables Status from
FSB_Status_Spreadsheet_V2.xls Organize by FSW
Testbed or other relevant product This chart
will be usable for SRR, PDR, CDR
10
FSW Deliverables Status
Insert FSW Team Deliveries Status from
FSB_Status_Spreadsheet_V2.xls Organize by FSW
Testbed, IT, or other cohesive manner This
chart will be usable for SRR, PDR, CDR
11
lt Project gt FSW Staff Plan vs Actuals

• Insert FSW Team Staff Plan vs Actuals graphic
  from FSB_Status_Spreadsheet_V2.xls
• .Staff associated with Development Test Team
  Leads is likely best completed by them with the
  PDL taking the data from them. This is to be a
  x.x FTE accuracy -- not hours. If on vacation for
  the full month and otherwise working full-time,
  the person is considered to be working as 1.0
  FTE. Show overtime as 1.y FTE (e.g., 1.1 FTE
  16 hrs. extra work beyond normal hours for the
  month).
• The intent is to have monthly data and a graphic
  that separates CS and SSC staff plans vs actuals
  with variances from the plan. How to do this is
  TBR.
• Also, how to track replans is TBR. For now
  provide plans submitted formally to the Project
  to Yvonne Lue (POPs replans)

e.g.,
Notes
12
lt Project gt FSW FundsPlan vs Actual
2 categories Task funds plan vs costs, and any
contracts/tasks issues. Breakout by CS and SSC??
Equipment and software tools costs.
13
lt Project gt FSW Staff Assignments

• This is currently intended to be the spreadsheet
  associated with the graphic 2 pages previous --
  Staff Plan vs Actuals spreadsheet from
  FSB_Status_Spreadsheet_V2.xls
• This is important for communications of staff
  commitments to your effort -- so that branch
  management understands availability for
  reassignments.
• This data could be in the DTL and TTL sections of
  status.

14
FSW Development Teams and Test Team Status
15
CDH FSW Development Team Accomplishments
Provide separate sheet for any diagnostics or
CDH simulation products being developed by FSW
team. Provide separate info. for each flight CPU.

• Last Months Plans for this month
• Cut and paste from last months status to 582
• Issues associated with the plan for this month
• This could include problems discovered,
  dependencies, unanticipated changes ,
• Accomplishments this month
• This should include words like initiated,
  delivered, completed, solved,
• Activities
• This may include words like continued,
  attempted, supported,
• Next Months Plans

16
CDH FSW Development Team Detailed Schedule (6
mos. - 1 yr.)
This could be a spreadsheet of people,
assignments, separate planned vs actual dates per
milestone for 6-12 mos. See example as
DevelMilestonePlanvsActuals w/in
FSB_Status_Spreadsheet_V2.xls .
17
CDH FSW Development TeamProgress Points
Enter point counting graphic.
18
CDH FSW Development Metrics

• Data should be available from ReqPro and MKS.
• Provide all data by per Subsystem and per Box
  (I.e., Main CDH, Main ACS, ACE CDH, )
• Capabilities Growth Plan vs Actual Prior to
  start of build development vs at Delivery to BT
  team
• Number of Reqmts. per build
• Number FSW Components per build
• Product Quality Cumulative Month by Month
• Number DCRs written against each build
• Number DCRs closed within each build
• Requirements Volatility Month by Month counts
  per subsystem per box
• Nbr. Reqmts. TBDs
• Nbr. Added
• Nbr. Deleted
• Nbr. Changed
• Total Nbr. Reqmts. by Subsystem
• Total Reqmts. per box

19
CDH FSW DevelopmentIssues, Concerns
20
CDH FSW Development Team Process Monitoring

• Indicate whether all current team members have
  had a facilitated walk-through of the key team
  documents.
• New staff must receive document WTs.
• Walk-through of Key Documents
• FSW Product Plan WT with all team members
  complete? Yes/No -- identify persons remaining
• FSW CM Plan DCR Process WT with all team
  members complete? Yes/No -- identify persons
  remaining
• FSW Test Plan WT with all team members
  complete? Yes/No -- identify persons remaining
• Peer Reviews
• ______________ Date Build Attending
  Prepared Duration Actions Closed
• e.g., Science support mm/dd/yy m n n x x
  x

21
ACS FSW Development Team Accomplishments
ltFlight CPU namegt
Provide separate info. for each flight CPU.

• Last Months Plans for this month
• Cut and paste from last months status to 582
• Issues associated with the plan for this month
• This could include problems discovered,
  dependencies, unanticipated changes ,
• Accomplishments this month
• This should include words like initiated,
  delivered, completed, solved,
• Activities
• This may include words like continued,
  attempted, supported,
• Next Months Plans

22
ACS FSW Development Team Detailed Schedule (6
mos. - 1 yr.)
This could be a spreadsheet of people,
assignments, separate planned vs actual dates per
milestone for 6-12 mos. See example as
DevelMilestonePlanvsActuals w/in
FSB_Status_Spreadsheet_V2.xls .
23
ACS FSW Development TeamProgress Points
Enter point counting graphic.
24
ACS FSW Development Metrics

• Data should be available from ReqPro and MKS.
• Provide all data by per Box (I.e., Main ACS, ACE,
  )
• Capabilities Growth Plan vs Actual Prior to
  start of build development vs At Delivery to BT
  team
• Number of Reqmts. per build
• Number FSW Components per build
• Product Quality Cumulative Month by Month
• Number DCRs written against each build
• Number DCRs closed within each build
• Requirements Volatility Month by Month counts
  per subsystem per box
• Nbr. Reqmts. TBDs
• Nbr. Added
• Nbr. Deleted
• Nbr. Changed
• Total Nbr. Reqmts. by Subsystem
• TOTAL Reqmts. per box

25
ACS FSW Development Issues, Concerns
Minimally, each yellow red item discussed
separately
26
ACS FSW Development Team Process Monitoring

• Indicate whether all current team members have
  had a facilitated walk-through of the key team
  documents.
• New staff must receive document WTs.
• Walk-through of Key Documents
• FSW Product Plan WT with all team
  members complete? Yes/No -- identify persons
  remaining
• FSW CM Plan DCR Process WT with all team
  members complete? Yes/No -- identify persons
  remaining
• FSW Test Plan WT with all team members
  complete? Yes/No -- identify persons remaining
• Peer Reviews
• ______________ Date Build Attending
  Prepared Duration Actions Closed
• e.g., Science support mm/dd/yy m n n x x
  x
• More is required -- TBD.
• Data Management

27
FSW Test Team Accomplishments
Provide separate info. for each flight CPU.

• Last Months Plans for this month
• Cut and paste from last months status to 582
• Issues associated with meeting the plan for this
  month
• This could include problems discovered,
  dependencies, unanticipated changes ,
• Accomplishments this month
• This should include words like initiated,
  delivered, completed, solved,
• Activities
• This may include words like continued,
  attempted, supported,
• Next Months Plans

28
FSW Test Team Detailed Schedule (6 mos. - 1 yr.)
This could be a spreadsheet of people,
assignments, separate planned vs actual dates per
milestone for 6-12 mos.
29
FSW Test TeamProgress Points
Enter point counting graphic for build test and
system test.
30
FSW Test Metrics

• TBR This should be worked among Tom Clement,
  Cindy Firman, Mo and Sara Haugh. .

31
FSW Test Issues, Concerns
32
FSW Test Team Process Monitoring

• Indicate whether all current team members have
  had a facilitated walk-through of the key team
  documents.
• New staff must receive document WTs.
• Walk-through of Key Documents
• FSW Product Plan WT with all team members
  complete? Yes/No -- identify persons remaining
• FSW CM Plan DCR Process WT with all team
  members complete? Yes/No -- identify persons
  remaining
• FSW Test Plan WT with all team members
  complete? Yes/No -- identify persons remaining
• Peer Reviews
• ______________ Date Build Attending
  Prepared Duration Actions Closed
• e.g., Science support mm/dd/yy m n n x x x
• More is required -- TBD.
• Data Management

33
FSW PDL wrap-up Slides(this slide is not
intended for inclusion in handout)
34
ltMissiongt Overall FSW Team Status

• Provide major highlights that would be
  presented to the Project.

35
FSW Product Metrics

• Data should be available from ReqPro and MKS.
• Collected data from indiv. subsystem and box
  statuses that would be presented to the Project.
• Capabilities Growth Plan vs Actual Prior to
  start of build development vs Delivery to BT team
• Number of Reqmts. per build
• Number FSW Components per build
• Requirements Volatility Month by Month counts
  per subsystem per box
• Nbr. Reqmts. TBDs
• Nbr. Added
• Nbr. Deleted
• Nbr. Changed
• Total Nbr. Reqmts. by Subsystem
• TOTAL Reqmts. per box
• DCR Status Month by Month counts per subsystem
  per box
• Nbr. DCRs New vs Open vs Closed -- by Severity
  (High, Med, Low)
• Length of time DCRs are Open -- by Severity

36
FSW Team Progress Tracking Status

• Provide Point Counting Graphic(s) here from
  _____(tool) as would be provided to the Project.
• Show earned value on a per subsystem/per box
  basis??

Notes Explain elements of the above graph that
need explaining.
37
FSW Product Team Issues/Concerns

• Technical
• Management

38
ltProjectgt FSW StatusBackup Charts and Format
prepare once, update over time as nec., show
dates of updates

• April 2005, 582 Baseline R2

39
FSW Status Backup Charts -- 1 each
For 582 mgmt. reference during status mtgs.
Provide once. Then provide updates, with update
dates, as appropriate.

• Mission/Instrument Overview -- orbit, mission
  life, Earth/Space science goals, major driving
  mission reqmts., C/D start Launch date,
• FSW Team Organization -- include Project
  reporting (PM, IM, )
• Baseline FSW Schedule (1-2 pg) at time of C/D
  staffing plan, and Replans
• Baseline Staff Plan Spreadsheet at time of C/D
  cost plan, and Replans
• Flight Data System Architecture (show data rates)
• FSW Architecture
• Key Flight H/W Resource Capabilities (CPU,
  memory, bus, SSR, )
• FSW Reuse/Heritage Summary (itemize)
• Development Tools
• Detailed Build Definitions per subsystem, per box
• Testbed Architectures -- show each testbed
  (devel., CDH, ACS, system test, instrument,
  power, .
• New Technologies