SOW_-_ACE_Agile_Quick_Reference_Guide.pdf
PDF 463 KB Posted
- Attached to
- Operational Test and Evaluation (OT&E) Support Federal contract opportunity
- Solicitation number
- HSBP1013R0080
About this file
File 2 refernced in SOW
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Amendment_A01_to_Solicitation_HSBP1013R0080.pdf | ||
| Solictation_with_changes.pdf | ||
| Questions_and_Responses_regarding_OTE_RFP.pdf | ||
| CUS1449_-_Commercial_Items_(SF1449).pdf | ||
| RFP_-_Att_C_-_Past_Perf_Questionnaire_V2.docx | DOCX document | |
| RFP_-_Att_A__-_CSPO_OTE_SOW_-_21_Aug.pdf | ||
| SOW_-_ACE_Roadmap_ACE_DevDepSched_v4-1_080613.xlsx | XLSX spreadsheet | |
| SOW_-_Executive_Overview_(EXS)_Cargo_Systems.pdf | ||
| SOW_-_Directive_026-06_Test_and_Evaluation_(Revision_00).pdf | ||
| SOW_-_ACE_Agile_Framework_v2.0_20130602.pdf | ||
| Synopsis_solictation.doc | DOC document | |
| RFP_-_Att_B_-_OTE_Support_Pricing_Template.xlsx | XLSX spreadsheet | |
| RFP_-_Att_A__-_CSPO_OTE_SOW.pdf | ||
| RFP_-_Att_C_-_Past_Perf_Questionnaire.docx | DOCX document |
Show all 14
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
OT&E
RRR Increment Timeline for each of the 12 ACE Increments
Each 2-Week Sprint
(Iteration)
Program Phase
Stage
Sprint Backlog Next Priorities that can be Done in 2 Weeks
Broken into Tasks of 4-6 Hours of Work per Person per Day
Operations & Maintenance Solution Engineering
Need Analyze/Select Obtain Deploy/Support
ADE
ADE
2A
5 Development Sprints (2 Weeks Each)
Definition of Done (DoD) Team Process Agreement (TPA) Product Backlog (PBK) = Hi-level
Requirements/User Stories & Estimates
• Increment Backlog (RBK) = Subset of
Product Backlog (PBK) for an Increment
• Increment / Release Planning Review
(RPR) Approval
• Documentation Updates
• Develop Team Process for Development, Test and Documentation
• Approve Test & Evaluation Master Plan
• Refine Product Backlog Estimate User Stories in Story Points
• Create Increment Backlog Sprint Review & Demo (SRD) for
Increment Planning
• Executive Steering Committee (ESC)
• Contract Negotiations (Labor Hours
Contract Type Recommended by OMB)
Ac tiv iti es
Ar tif ac ts
• Increment Backlog (RBK) Sprint Backlog (SBK) = Subset of Product Backlog (PBK) and Increment
Backlog (RBK) for a Sprint
• Sprint Review & Demo (SRD) Letter
• System Design Document (SDD)
• Security Artifacts (SR, SAR, POA&M) Information Radiators such as Taskboards, Burnup and Burndown Charts
[to Fulfill Similar Reporting Function to Earned Value Management (EVM)]
• Documentation Updates
Sprint Planning Meeting Daily Scrum Meetings
• Requirements Management
• Mock-ups, Use Cases, Simulations, and Prototyping (if needed)
• Develop, Test & Review Code, Test Cases and Test Scripts
• Compliance Bodies Participate as Defined in the TEMP, TPA Update Progress Reports for Transparency Sprint Review & Demo (SRD) Sprint Retrospective
• Acceptance Test Readiness Review (ATRR) / Integration Readiness
Review (IRR)
• Test Reports
• Deployment Plans
• Increment / Release Readiness Review
(RRR) Approval
• Updates to SDD, Security Artifacts
• Final Acceptance Testing (SAT, UAT, 508, ST&E)
• Regression Testing
• Deployment Planning and Preparation
• Data Migration or Setup
• POA&M
• Receipt of Authority to Operate (ATO)
• Release Readiness Review (RRR) /
RRR Increment (RRRi) / Production Readiness Review (PRR) at Executive Steering Committee (ESC)
• Operational Test & Evaluation (OT&E)
• Measure Performance and Results
• Post Implementation Review (PIR)
• Maintenance and Enhancements Feed Product Backlog
• Operational Plan
• Post Implementation
Review (PIR) Results and Report
• Update Artifacts as Necessary
Mission Need Statement (MNS) Executive Summary (EXS) Operation Requirements Doc (ORD) Concept of Operations (CONOPS) Cost Estimating Baseline Doc (CEBD)
• Life Cycle Cost Estimate (LCCE)
• Acquisition Program Baseline (APB)
• Acquisition Plan (AP) Program Oversight Plan (POP)
• PMP/IMS, ILSP, TEMP, Tailoring Plan
• Systems Engineering Plan (SEP)
• Identify Capabilities to Fulfill Mission Needs & Constraints
• Explore Possible Solutions
• Select Solution & Acquisition Strategy
• Develop Business Case
• Plan Oversight/Governance Approach
• Architecture Alignment & Assessment
(AAA)
• Acquisition Decision Event (ADE)-2A
• Acquisition Decision Event (ADE)-2B
ACE Agile Software Development Quick Reference Guide Rev Date: 06/05/2013
PIR
Individuals and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to Change over Following a Plan
Agile Manifesto Values
Faster Time to Market Reduced Cost (Streamlined Documentation, Fail & Catch Defects
Early in Life Cycle, Avoid Unused Features - 43% Historically) Reduced Project Risk (Continual Customer/User Collaboration) Ability to Respond to Customer and Requirement Changes
Agile Benefits
• Hi-Level Descriptions of Requirements, Needs & Constraints
• In Everyday Business Language of the End User
• Features Decomposed into User Stories during Increment Planning
• User Story: As Role X, I want the System to do Y, for Value Z
• Independent, Negotiable, Valuable, Estimatable, Small, Testable
(INVEST) Requirements
• Expected and Encouraged to Emerge and Change
• Continually Prioritized in Order by the Product Owner (OT/ABO)
• Includes both New Functionality Changes and Break/Fix Problem
Reports (PRs)
Product Backlog of Themes & Features
• Defines Features of the Product in User Stories
• Prioritizes Features According to Mission Value
• Approves Shippable Increments for Release to Production
• Responsible for Product Value/Return on Investment (ROI)
• Empowered to Accept or Reject Work Products/Results
• Adjusts Features and Priorities after every Sprint (Iteration)
Product Owner / Capability Owners (OT/OFO)
• Facilitates Agile/Scrum Team Process, Values and Meetings
• Responsible for Coordination, Training and Documentation
• Removes Obstacles & Shields from External Interferences
Agile Team Lead (OIT Scrum Master)
Product Backlog 4-6 Hour Tasks Features
Sprint 2 Weeks
Working Software
Sprint Planning Meeting Review Product Backlog Establish and Estimate Sprint
Backlog for Priorities & Capacity Commit to 2-4 Weeks of Work
Daily 15-min Scrum Meeting Done Yesterday Plan for Today Obstacles, Interferences or Dependencies?
Sprint Review and Demo Definition of Done Achieved?
Demo “Done” Functionality Update Information Radiators Feedback for Backlog
Daily
P R I O R I T I Z E D
Product Owner (OT)
Customer/Stakeholders
Resulting in Production Ready Software
Enhancements Defects/PRs
User Stories to Product Backlog
Mission Needs & Constraints
Features & Requirements
ACE Agile Team (Self-Organizing)
Top User Stories
ADE
Gate
Executive Steering
Committee
ADE
In te gr at e
Sprint Retrospective What Worked?
What didn’t Work?
Improvements for Next Sprint?
Sprint 0 Sprint 1 Sprint 2 Sprint 3
SRD SRD
Sprint 4 Sprint 5
SRD
Sprint 6
SRD SRD SRD
Increment Planning (1 Week)
ADE
2B
Hardening
Sprint
ATRR
13-Week Increment Timeline
ESC
3 Production Ready Software Deployment Options:
1. Deploy after RRR
2. RRR + 13 Weeks (Trade Dependency)
3. RRR + 26 Weeks (Significant Security Testing)
Solution Engineering Sprint 0 – Increment Planning Sprints 1-5 – Development Sprints Sprint 6 – Hardening / Integration Operations & Maintenance
ATO
ACE Agile 101 Training
Production Ready Software
ADE
2C
Capability Owner (OT/OFO Govt.)
Agile Team Lead (OIT Govt.)
Cross-Functional Team 2 SMEs (Govt.)
3-5 Developers (Cont.)
2 Testers (Govt./Cont.)
1 SE (Govt./Cont.)
SRD
15 ACE
Agile
Teams
ADE
3 OTRR
For Each Deployment https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Backlog Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Definition of Done (DoD) Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/ACE Team Process Agreement (TPA).docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Product Backlog Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/User Stories Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/User Stories Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Backlog Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Information Radiators Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Agile Management Reporting Process.doc https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Agile Management Reporting Process.doc https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Planning Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Daily Scrum Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Agile Management Reporting Process.doc https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Retrospective Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Mission Needs Statement_ACE.doc https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Executive Overview (EXS)_Cargo Systems.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Executive Overview (EXS)_Cargo Systems.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Operational Requirements Document (ORD)_ACE.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Concept of Operations (CONOPS)_ ACE.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Cost Estimating Baseline Document (CEBD)_ACE.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Program Oversight Plan (POP)_Cargo Systems.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Cargo Systems Program Oversight Plan (POP).docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/ADE2A 2B/Integrated Logistics Support Plan (ILSP)_ACE.docx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Product Backlog Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/User Stories Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Execution Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Planning Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Daily Scrum Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Execution Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/User Stories Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/User Stories Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Retrospective Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/ACE Agile 101 Overview.pptx https://cbpnetsecure.cbp.dhs.gov/sites/OIT/CSPO/PGC/PML/Sprint Review and Demo Meeting Tips.pptx
Slide Number 1
OT&E
RRR
Increment
Timeline for each of the 12 ACE
Increments
Each
2-Week
Sprint
(Iteration)
Program Phase
Stage
Sprint Backlog
Next Priorities that can be Done in 2 Weeks
Broken into Tasks of 4-6 Hours of Work per Person per Day
Operations &
Maintenance
Solution Engineering
Need
Analyze/Select
Obtain
Deploy/Support
ADE
ADE
2A
5 Development Sprints
(2 Weeks Each)
Definition of Done (DoD)
Team Process Agreement (TPA)
Product Backlog (PBK) = Hi-level Requirements/User Stories & Estimates
Increment Backlog (RBK) = Subset of Product Backlog (PBK) for an Increment
Increment / Release Planning Review (RPR) Approval
Documentation Updates
Develop Team Process for Development, Test and Documentation
Approve Test & Evaluation Master Plan
Refine Product Backlog
Estimate User Stories in Story Points
Create Increment Backlog
Sprint Review & Demo (SRD) for Increment Planning
Executive Steering Committee (ESC)
Contract Negotiations (Labor Hours Contract Type Recommended by OMB)
Activities
Artifacts
Increment Backlog (RBK)
Sprint Backlog (SBK) = Subset of Product Backlog (PBK) and Increment Backlog (RBK) for a Sprint
Sprint Review & Demo (SRD) Letter
System Design Document (SDD)
Security Artifacts (SR, SAR, POA&M)
Information Radiators such as Taskboards, Burnup and Burndown Charts [to Fulfill Similar Reporting Function to Earned Value Management (EVM)]
Documentation Updates
Sprint Planning Meeting
Daily Scrum Meetings
Requirements Management
Mock-ups, Use Cases, Simulations, and Prototyping (if needed)
Develop, Test & Review Code, Test Cases and Test Scripts
Compliance Bodies Participate as Defined in the TEMP, TPA
Update Progress Reports for Transparency
Sprint Review & Demo (SRD)
Sprint Retrospective
Acceptance Test Readiness Review (ATRR) / Integration Readiness Review (IRR)
Test Reports
Deployment Plans
Increment / Release Readiness Review (RRR) Approval
Updates to SDD, Security Artifacts
Final Acceptance Testing (SAT, UAT, 508, ST&E)
Regression Testing
Deployment Planning and Preparation
Data Migration or Setup
POA&M
Receipt of Authority to Operate (ATO)
Release Readiness Review (RRR) / RRR Increment (RRRi) / Production Readiness Review (PRR) at Executive Steering Committee (ESC)
Operational Test & Evaluation (OT&E)
Measure Performance and Results
Post Implementation Review (PIR)
Maintenance and Enhancements Feed Product Backlog
Operational Plan
Post Implementation Review (PIR) Results and Report
Update Artifacts as Necessary
Mission Need Statement (MNS)
Executive Summary (EXS)
Operation Requirements Doc (ORD)
Concept of Operations (CONOPS)
Cost Estimating Baseline Doc (CEBD)
Life Cycle Cost Estimate (LCCE)
Acquisition Program Baseline (APB)
Acquisition Plan (AP)
Program Oversight Plan (POP)
PMP/IMS, ILSP, TEMP, Tailoring Plan
Systems Engineering Plan (SEP)
Identify Capabilities to Fulfill Mission Needs & Constraints
Explore Possible Solutions
Select Solution & Acquisition Strategy
Develop Business Case
Plan Oversight/Governance Approach
Architecture Alignment & Assessment (AAA)
Acquisition Decision Event (ADE)-2A
Acquisition Decision Event (ADE)-2B
ACE Agile Software Development Quick Reference Guide
Rev Date: 06/05/2013
PIR
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation
Responding to Change over Following a Plan
Agile Manifesto Values
Faster Time to Market
Reduced Cost (Streamlined Documentation, Fail & Catch Defects Early in Life Cycle, Avoid Unused Features - 43% Historically)
Reduced Project Risk (Continual Customer/User Collaboration)
Ability to Respond to Customer and Requirement Changes
Agile Benefits
Hi-Level Descriptions of Requirements, Needs & Constraints
In Everyday Business Language of the End User
Features Decomposed into User Stories during Increment Planning
User Story: As Role X, I want the System to do Y, for Value Z
Independent, Negotiable, Valuable, Estimatable, Small, Testable (INVEST) Requirements
Expected and Encouraged to Emerge and Change
Continually Prioritized in Order by the Product Owner (OT/ABO)
Includes both New Functionality Changes and Break/Fix Problem Reports (PRs)
Product Backlog of Themes & Features
Defines Features of the Product in User Stories
Prioritizes Features According to Mission Value
Approves Shippable Increments for Release to Production
Responsible for Product Value/Return on Investment (ROI)
Empowered to Accept or Reject Work Products/Results
Adjusts Features and Priorities after every Sprint (Iteration)
Product Owner / Capability Owners (OT/OFO)
Facilitates Agile/Scrum Team Process, Values and Meetings
Responsible for Coordination, Training and Documentation
Removes Obstacles & Shields from External Interferences
Agile Team Lead (OIT Scrum Master)
Product Backlog
4-6 Hour Tasks
Features
2 Weeks
Working Software
Sprint Planning Meeting
Review Product Backlog
Establish and Estimate Sprint Backlog for Priorities & Capacity
Commit to 2-4 Weeks of Work
Daily 15-min Scrum Meeting
Done Yesterday
Plan for Today
Obstacles, Interferences or Dependencies?
Sprint Review and Demo
Definition of Done Achieved?
Demo “Done” Functionality
Update Information Radiators
Feedback for Backlog
Daily
P
R
I
O
R
I
T
I
Z
E
D
Product Owner (OT)
Customer/Stakeholders
Resulting in Production Ready Software
Enhancements
Defects/PRs
User Stories to Product Backlog
Mission Needs
& Constraints
Features &
Requirements
Develop
Test
Design
ACE Agile Team (Self-Organizing)
Top User Stories
ADE
Gate
Executive
Steering
Committee
Integrate
Sprint Retrospective
What Worked?
What didn’t Work?
Improvements for Next Sprint?
Sprint 0
Sprint 1
Sprint 2
Sprint 3
SRD
SRD
Sprint 4
Sprint 5
SRD
Sprint 6
SRD
SRD
SRD
Increment
Planning
(1 Week)
2B
Hardening
ATRR
13-Week Increment Timeline
ESC
3 Production Ready Software
Deployment Options:
1. Deploy after RRR
2. RRR + 13 Weeks
(Trade Dependency)
3. RRR + 26 Weeks
(Significant Security Testing)
Solution Engineering
Sprint 0 – Increment Planning
Sprints 1-5 – Development Sprints
Sprint 6 – Hardening / Integration
Operations & Maintenance
ATO
ACE Agile 101 Training
Production
Ready Software
2C
Capability Owner
(OT/OFO Govt.)
Agile Team
Lead (OIT Govt.)
Cross-Functional Team
2 SMEs (Govt.)
3-5 Developers (Cont.)
2 Testers (Govt./Cont.)
1 SE (Govt./Cont.)
SRD
15 ACE Agile Teams
OTRR
For Each
Deployment image2.png image3.png image4.png image5.emf image1.png
File details come from the government source that posted it. Updated .