1 1-Introduction 2-What/Why is Agile? 3-Basic Agile Concepts 4-Effects of Agile on Program Office Staff 5-Effects of Agile on Engineering Staff 6-Effects.

Slides:

Advertisements

Similar presentations

© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v

Advertisements

SEMP vs. PMP Conflict and Partnership

Subtracting Polynomials. Lets review Copy the following expressions and then write the opposite of each one. 1. 2y x 2 +5x m 2 -m+3.

Technology Module: Technology Readiness Levels (TRLs) Space Systems Engineering, version 1.0 SOURCE INFORMATION: The material contained in this lecture.

TechMIS LLC Proprietary Tracking Requirements And Compliance Engineering (TRACE ) Steve Collier/B. Squires/TechMIS LLC An affordable and user friendly.

IRM 101 Critical Design Review For March 2015 Update Status 11/21/2014.

Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.

LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.

Security Assessments FITSP-M Module 5. Security control assessments are not about checklists, simple pass-fail results, or generating paperwork to pass.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.

Project Management An Overview John Mulhall MIICM; LIB International Credit & Process Management Professional.

Tyson’s Approach to Organizational Change Management

Security Assessments FITSP-A Module 5

BSBPMG502A Manage Project Scope 5.3 Create Work Breakdown Structure The process of sub dividing project deliverables and project work into smaller, more.

Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.

『华东师范大学』课程名称：软件开发实践 Software Development Practice 课程类型：实践课第二讲：项目管理 Lect_02: Manage the Project 主讲 : 软件学院周勇副教授日期 :

Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.

IT Requirements Management Balancing Needs and Expectations.

Michael deLamare Requirements Management Program Functions R-9.

SOFTWARE DESIGN Design Concepts Design is a meaningful engineering representation of something that is to be built It can be traced to a customer’s requirements.

Introduction Training on Safe Hospitals in Disasters.

Course priorities How it works 1. Plot a dot on the vertical length of the line for each of the topics. The further out your dot, the more important that.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.

Scope Management Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 5 Learning Objectives After completing this chapter,

Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall o P.I.I.M.T o American University of Leadership Ahmed Hanane, MBA, Eng, CMA, Partner.

Vers national spatial data infrastructure training program What is Metadata? Introduction to Metadata An overview of geospatial metadata, presentation.

Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.

International Atomic Energy Agency Irina Sanda Education and Training in the Area of Safety Assessment Irina Sanda Safety Assessment Section Division of.

CLE 076 Introduction to Agile Software Acquisition CLE Introduction to Agile Software Acquisition1.

CLE 076 Development Team Meeting #2 12/4/2015 CLE Introduction to Agile Software Acquisition1.

#7-Effect of Agile on Post-Contract Award Subtopics #1- Documentation #2- Regulatory oversight #3- Participating in Agile reviews #4- Measurement ELO ELO.

Defense Business Systems (CLE077) Sprint November 9, 2015 DRAFT1 Sprint Working Group Toni Freeland Kevin Hamilton Lee Hewitt Tom Hickok Len Nale Bob Ramsey.

#7-Effect of Agile on Post-Contract Award Subtopics Documentation Regulatory oversight IBR Participating in Agile reviews Performance Measurement ELO ELO.

Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.

CLE 076 Introduction to Agile Software Acquisition CLE Introduction to Agile Software Acquisition1.

#6- Effects of Agile on Pre-Contract Award Subtopics Acquisition Strategy Writing RFP’s allowing for Agile IPM Methodology Evaluating Bidders in Agile.

Module 3: Basic Agile Concepts – when and where to apply it TLO: Given a contractor’s development approach student will recognize alignment with agile.

Table of Contents – Module 0 Overview of files associated with the Cloud CLM CLE - Module 0 - CLM Table of Contents1.

EXAMPLE 1 Add polynomials vertically and horizontally a. Add 2x 3 – 5x 2 + 3x – 9 and x 3 + 6x in a vertical format. SOLUTION a. 2x 3 – 5x 2 + 3x.

90 Vertical Horizontal Oblique line a b Angles a + b = 180 o Angles at a Point b = 115 o Angle a = 180 – 115 = 65 o.

V. 2. © Copyright and all rights reserved 4. Project Integration Management PMP Prep Course Based on the PMBOK ® Guide 3 rd Edition.

Module 5: Effect of Agile on Engineering & Test Staff TLO: Given a DoD program involved in software development using Agile IPM methodologies, the student.

GAO’s Cost and Schedule Assessment Guides U.S. Government Accountability Office Applied Research and Methods Cost Engineering Sciences Jason T Lee, Assistant.

Module 7: Effect of Agile on Post-Contract Award TLO: Given a DoD program involved in software development using Agile philosophy, the student will identify.

Office 365 FastTrack Planning Engagement Kickoff.

Module 4: Effect of Agile on the DoD Program Office TLO: Given a DoD program involved in software development using Agile philosophy methodologies, the.

CLE Introduction to Agile Software Acquisition

CLE Introduction to Agile Software Acquisition

5 – Effect of Agile on Engineering & Test Staff

Oral and Written Presentations

Module 1 Review of Data Collection and Analysis Concepts

Individual Thinking Time

Writing Product Requirements

CMQ101 - Course Introduction

ISA 201 Intermediate Information Systems Acquisition

#2-What is Agile? Why Agile?

Infrastructure Delivery Management Toolkit:

Defense Business Systems (CLE077) Sprint

Defining the Activities

Project or Team name: Vision: Mission Statement:

ECE 3000: Engineering Seminar

Design Model Like a Pyramid Component Level Design i n t e r f a c d s

Education and Training in the Area of Safety Assessment Irina Sanda

Writing Product Requirements

Department of Navy Rapid Innovation Fund

Work Breakdown Structure Tasks and Sub-Tasks

Presentation transcript:

1 1-Introduction 2-What/Why is Agile? 3-Basic Agile Concepts 4-Effects of Agile on Program Office Staff 5-Effects of Agile on Engineering Staff 6-Effects of Agile on Pre-Contract Award 7-Effects of Agile on Post-Contract Award 8-Enabling an Agile Acquisition Culture 9-Summary CLE 076 Modules

Module 1 – What is Agile ELO1 ELO2 ELO3 2

Module 5-Effects of Agile on Engineering Staff ELO1 Identify/list/describe/discuss/recognize ELO2 … ELO3 Identify how program technical requirements are expressed in Agile contracting settings. ELO4Identify how requirements are traced in Agile contracting settings. 3

Topic 1 Topic 2 Expressing requirements in Agile contracting settings Horizontal and Vertical Traceability in Agile contracting settings Topic 5 Topic 6 …. Module 5 : Effects of Agile on Engineering Staff 4

ELO 1: MT 1 MT 2 MT n ELO 2: MT 1 MT 2 MT n ELO 3: Identify how program technical requirements are expressed in Agile contracting settings. 3.MT1 A requirements baseline that is at too low a level of abstraction is unproductive for an Agile contract setting. 3.MT 2 In Agile settings, low level requirements add who and why to the typical what of requirements, often using a format called a “story” 3.MT 3 A capability-based Work Breakdown Structure makes developing and refining requirements in an Agile setting easier than using the more hardware-focused, but typical, component- based WBS 3.MT 4 Requirements in an Agile contracting setting need to be prioritized in terms of the rank order of their value to the end use and other stakeholders. Module 5 : Effects of Agile on Engineering Staff 5

Sub Topic ELO: Content Assessment 6 Expressing requirements in Agile contracting settings Identify how program technical requirements are expressed in Agile contracting settings. Module 5 : Effects of Agile on Engineering Staff A requirements baseline that is at too low a level of abstraction is unproductive for an Agile contract setting. From a list, choose the level of requirements that is appropriate for establishing a technical baseline.