ipr the agile team

14
IPR The Agile Team Christina Gu Jason Lee Stephen Smith

Upload: penny

Post on 05-Jan-2016

32 views

Category:

Documents


0 download

DESCRIPTION

IPR The Agile Team. Christina Gu Jason Lee Stephen Smith. Outline. -Project Overview -Milestone Status -Continuing Research Effort - Work to be Done -Issue Detail -Earn Value Analysis. PROBLEM STATEMENT RECAP: Are there benefits from using Agile Software - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: IPR The Agile Team

IPRThe Agile Team

Christina GuJason LeeStephen Smith

Page 2: IPR The Agile Team

Outline-Project Overview-Milestone Status-Continuing Research Effort-Work to be Done-Issue Detail-Earn Value Analysis

Page 3: IPR The Agile Team

Project OverviewPROBLEM STATEMENT RECAP:

Are there benefits from using Agile SoftwareDevelopment methodologies versus Waterfall and

Spiral in the Context of Systems Engineering Products

Compare Agile with traditional Systems Engineering in terms of: Cost, Schedule, and Quality

Page 4: IPR The Agile Team

MILESTONE STATUS Table Name Planned Finish Actual STATUS

THE AGILE TEAM Fri 5/10/13 Fri 5/10/13

Problem Definition Mon 2/4/13 Mon 2/4/13

Project Proposal Mon 2/18/13 Mon 2/18/13

Written Proposal Mon 2/25/13 Mon 2/25/13

Finalize Scope Mon 3/4/13 Mon 3/25/13

Meet with Sponsor Thu 3/7/13 Thu 3/7/13

Negotiate Scope Thu 3/14/13 Thu 3/21/13

Get Stakeholder Buy-in on Scope Definition

Mon 3/4/13 Mon 3/25/13

Website Mon 3/11/13 Mon 3/11/13

IPR Mon 3/18/13 Mon 3/18/13

Metrics Development Mon 3/25/13 Thu 3/28/13

Team Meeting with Professor Mon 4/1/13 Mon 4/1/13

Meeting: Status w/ Professor

Mon 4/1/13 Mon 4/1/13

Data Analysis Mon 4/15/13 Mon 4/15/13

Final Report Fri 4/26/13 Fri 4/26/13

Present Report to Sponsor Fri 4/26/13 Fri 4/26/13

Final Presentation Fri 5/10/13 Fri 5/10/13

Legend:Completed on time

Delayed

on Schedule

Page 5: IPR The Agile Team

What was Done

Presentation of Results

Clear, Robust, Concise, Persuasive

Analysis of DataWhat the data really says

Development of Evaluation MetricsInvolve Sponsor to support Metrics

Research and Information GatheringData suitable for analysis

Getting a clear understanding of the sponsor’s needs and scoping down the problem to satisfy all of the Stakeholders involved.

Page 6: IPR The Agile Team

• Met with sponsor for clear direction on their needs for the project

• The results were that the sponsor wanted more research into how documentation is affected by Scrum Agile development

• The sponsor wanted the effort to be more general, not Boeing-specific

• Redirected research efforts to align with new sponsor direction

What was Done-cont.

Page 7: IPR The Agile Team

Narrowing MIL-STD-498 to most applicable systems engineer documents:

• Requirements: SSS, SRS, IRS• Design: SSDD, SDD, IDD• Qualification/Test: STP, STD• Operational Manuals: SUM• Software Manuals: SVD

The research is now focused on Agile methods of developing these specific documents.The research includes methodologies for including documentation as part of the Agile development cycle.

Research Efforts

Page 8: IPR The Agile Team

More input is needed from various stakeholdersResearch on individual documentation generation using AgileGenerating a characterization of each documentation

• How is it generated• When is it generated• What it’s used for• Is it different from a traditionally developed document?• Does the documentation ownership change?

What Needs to be Done

Page 9: IPR The Agile Team

What Still Needs to be Done

• A cost analysis on documents generated using Agile based on research found on schedule differences.

• Will be done with hypothetical cost data numbers due to sponsor data limitation.

• The cost/schedule analysis is secondary and may be scoped out with further discussion with sponsor.

Page 10: IPR The Agile Team

Issue Detail

Issue 1: Scope• Description: tied directly to

our primary risk: Scope• Impact: Continued

deliberation with stakeholders delays project schedule

• Team Action: Assigned team Issue 1 owner– Key resources: Team 6,

Boeing, GMU Faculty– Resolution Deadline: 3/25/13

Issue 2: Restricted Schedule

• Description: Scope changes have pushed schedule back

• Impact: More work to be done by the team, in less time

• Team Action: Increase burn rate to make up schedule loss– Key resource: Team 6 time

investment– Resolution Deadline: 4/19/13

Page 11: IPR The Agile Team

Earned Value Analysis

Jan Feb Mar Apr MayBudget at Completion (BAC) $39,375 $39,375 $39,375 $39,375 $39,375Earned Value (EV) $2,625 $9,450Actual Cost (AC) $2,063 $10,313Planned Value (PV) $2,625 $13,125 $23,625 $34,125 $39,375Cost Variance (CV) $563 ($863) $0 $0 $0Schedule Variance (SV) $0 ($3,675) ($23,625) ($34,125) ($39,375)Cost Performance Index (CPI) 1.27 0.92Schedule Performance Index (SPI) 1.00 0.72 0.00 0.00 0.00Estimate to Completion (ETC) $28,875 $32,656Estimate at Completion (EAC) $30,938 $42,969Variance at Completion (VAC) $8,438 ($3,594)Status based on Average Performance Index

GREEN RED

Comments

Project Earned Value AnalysisThe Agile Project

Page 12: IPR The Agile Team

Questions?

Page 13: IPR The Agile Team

Backup: EV Trend Analysis

Page 14: IPR The Agile Team

Backup: EV Trend Analysis