# Presentation: 311581

## 
July 21, 2005

Presented by: Ella Page
Software Process Improvement (SPI) Project

**July 21, 2005**
**Presented by: Ella Page**
***Software Process Improvement (SPI) Project***

**The New ISD BSR –****What you Need to Know**

## Purpose and Objectives

**Purpose: To provide an overview of the new bi-monthly MSR template reporting requirements **
**The Branch (*****or Division)***** Status Review (BSR)**
**Objective -  After this session you should know:**
**What information is required in a BSR**
**How to effectively present the information on BSR charts**
**Some of the dos and don’ts in preparing a BSR presentation**

## The ISD Branch Status Review Template

**Where can you find the BSR template?**
**Go To *****http://software.gsfc.nasa.gov/ISDpaIndx.cfm***
**See Asset 1.4.3.4, ISD Branch Status Review Template**
**What’s in the asset?**
**Template Purpose, Scope, and Tailoring information (pages 1-2)**
**Template for preparing a BSR (pages 3-16)**
**BSR Template Guidance (pages 17-37)**
**When do you have to use it?**
**Now!**

## BSR Content Overview

**What’s in the BSR? *********
**Overall Project Status**
**Project Staffing Summary and Schedule Information**
**General Software Project Status **
**Accomplishments**
**Deliverables**
**Receivables**
**Commitments**
**Technical and Management Issues and Concerns**
**Software Project Risk Status**
**Software Project Metrics**

****** This is information you should use in managing your project, so you should have all the data at hand as you create the slides. ***

## Overall Project Status

**Summarize the overall state of the project in 1 page**
**Set the stage for the review**
***Focus on your message(s) for management ***
**Messages are the key “good” points and the key risk or problem areas**

**Provide a “Red/Yellow/Green” chart that covers 3 reporting periods (last 2 and current)**
**You set up the boxes and the “color” criteria**
**Update project status based on the approved criteria**

## Project Staffing Summary

**Project Staffing Summary**

***Show planned versus actual staffing***
**Planned data comes from your project plan**
**Actual data comes from WebTADs for civil servants, or it comes from contractors**

- Identify why you have a variance (such as changes in requirements, budget).
- Identify the impact of variance
- Identify corrective actions planned or taken.

**Show FTE data ****monthly****, **
**cumulatively****, **
** ****or both ways **

**Provide a text box with staffing analysis***

## Project Schedule Overview 

**Get schedule information from your project plan**
**Get progress data from your measurement activities**
**Show actual progress against planned progress**

**Project Schedule Overview **

- Planned Activities and Milestones

- Actual progress against the plan

- Current time

## Software Project Detailed Status 

**Include technical and support milestones**
**Get schedule information from your ****software ****project plan**
**Get progress data from your measurement activities**
**Show current progress against the plan**

**Software Project Detailed Status **

## Detailed Support Activities

**These represent the support details that should be included in your schedule**
**Each support area *****must***** be addressed with some process activities *****as appropriate to the current phase***** **
**Provide details of work planned and accomplished**

## General Software Project Status - Accomplishments

**Describe what was planned for this period**
**Describe accomplishments for this period**
**Describe plans for next period**
**Report on technical areas, including**
**Completing products**
**Technical activities**
**Meeting milestones**
**Supporting customer events**
**Report on support (i.e., process) areas, including**
**Software Project planning**
**Software Project monitoring and control**
**Supplier agreement management**
**Process and product quality assurance**
**Configuration management**
**Requirements management**
**Measurement and analysis**

## Sample Accomplishments Slide

**Base planned and accomplished description on CURRENT reporting period only.**
**Based future plans on next reporting period only.**

- Use short bulleted phrases

## General Software Project Status – Deliverables / Receivables / Commitments

**List all project deliverables, receivables, and commitments **
**For the current reporting period**
**For at least the next two reporting periods (and further in the future if of particular criticality or interest (for example, deliver to I&T)**
**Minimum information must include**
**Name of the deliverable, receivable, or commitment item**
**An indicator of the type of item (i.e., deliverable, receivable, or commitment)**
**Both planned and actual dates for each item**

***Consider using the following table to provide this information.  Other formats are acceptable as long as they include the requisite information.***

## Issues and Concerns

**Address the software project’s issues and concerns including, at a minimum:**
**A brief description of the issue/concern**
**An analysis of the issue/concern**
**Specific impact(s) on your software project**
**Specific internal and external stakeholders who are affected or should be involved in the resolution process**
**Separate technical and management issues and concerns**
**Management issues worked by PDL and management**
**Technical issues worked by technical teams**
**Use a format that can fully describe the required items**

## Issues and Concerns Suggested Format

**Issues and Concerns Suggested Format**

**One Issue/Concern per slide**
**Show required information:**
**A brief description of the issue/concern**
**An analysis of the issue/concern**
**Specific impact on your project**
**Be sure to note where specific internal and external stakeholders are involved**

## Software Project Risk Status

**Provide a summary of each *****major***** software project risk and a risk matrix**
**Include, at a minimum, all “RED” risks **
**Present a clear, concise statement of: **
**The risk mitigation strategy**
**Date last revisited**
**Status information such as**
**Current activities **
**Time period that risk is active**
**Event/date that triggers the risk’s mitigation**

## Software Project Metrics

**Include slides that address all measures specific to your software project, including Risk Management Metrics**
**See *****http://software.gsfc.nasa.gov/MeasProj.htm****** for information on measurement for software projects***
**See *****http://software.gsfc.nasa.gov/discussionslides.cfm***** for Measurement and Analysis for ISD Software Projects  presentation**
**Use charts or graphs to show data**
**Include a short analysis description**

## Example Slides for Project Metrics

## Example Requirements Volatility Chart

## Example Risk Metrics Chart

## Outline of a Tailored BSR for FSW 

**FSW Status Summary**
**FSW Significant Events**
**FSW System Engineering Activities**
**FSW Schedule Overview**
**FSW Risks**
**FSW Status of documents, receivables, deliverables**
**FSW Staffing – Planned Versus Actuals**
**FSW Staffing Assignments**
**FSW Development and Test Teams’ Status**
**Accomplishments**
**Detailed Schedule**
**Metrics (Point Counts and other metrics)**
**Issues and Concerns**
**Process Monitoring**

## BSR Dos and Don’ts

**Do remember to report the good news as well as the problems**
**Do focus on the CURRENT reporting period progress and next period plans**
**Do understand the metric data needed – collect and analyze it regularly**
**Don’t forget to report on activity (process) status as well as product status**
**Don’t report the “nitty-gritty” details – this is a management-level review**
**Don’t forget to report the problems and issues – get management help if needed**
**Don’t try to remember everything at the end of the month ... make notes along the way**

## Summary

**Make sure you present the required information **
**Use the ISD Branch Status Review Template, Asset 1.4.3.4, as a guide**
**Use your organization’s template as a guide**
**Keep your focus at a high level except for high impact issues, concerns, and risks**
**Report progress on both technical and support activities relative to plan**
**Collect your metric data as you go and the report will be easy to put together**
**Analyze the metric data and understand the impact of the numbers – you need this to manage your project**
**Use tools like Excel spreadsheets to create your charts when possible**
**Tailor your reporting approach to the software classification and size**

## Getting Help for Your BSR

**Get help when you need it**
**Sally Godfrey – Software Process Improvement Manager**
***Sara.H.Godfrey@nasa.gov ***
**Sanjeev Sharma – Software Process Improvement**
***Sanjeev.K.Sharma@nasa.gov***

## Questions?

## July 21, 2005 – Using the website http://software.gsfc.nasa.gov/

***July 21, 2005 – Using the website ******http://software.gsfc.nasa.gov/***

**Click asset name to get asset PDF**

**Click “?” to get feedback form**

**Click icons for desired files**

**Use search function to find assets**

**Use approved process assets**

**Find tools**

**Get measurement info**

**See lessons learned**

**Locate training and experts**

**See Engineering process group (EPG) Contacts**

## July 21, 2005 – Accessing Presentation Slides From the Website

**Access SW Engineering Discussion schedule:**
***(http://software.gsfc.nasa.gov/swengdisc.cfm)***

**Access slides from past SW Engineering Discussions:**
***(http://software.gsfc.nasa.gov/swengdisc.cfm)***

**For SW Engineering Discussions ...**
**   ****Click “Training” and highlight **
**   “*****S/W Eng. Discussions*****”**

**Access slides from other useful presentations**

**For Other On-Line Slides...**
**   ****Click “Training” and highlight **
**   “*****Training Program*****”**