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

Slides:



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

Planning Iterative Software Development Projects Raj Agrawal, PMP Unisys.
Systems Engineering in a System of Systems Context
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
IRM 101 Critical Design Review For March 2015 Update Status 11/21/2014.
CP methodology adapted to Stockholm Convention Swedish International Development Agency S ESSION 9.C United Nations Environment Program Division of Technology.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Acquiring Information Systems and Applications
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY The current state of stakeholder-driven requirements engineering.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
BEFORE AGILE METHODS Other Engineering fields development models were used, ie: Waterfall Method: Intensive planning and refactoring before coding is actually.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
NDIA Software Committee Paul R. Croll, CSC Michael H. McLendon, OSD/DDR&E/SE NDIA Systems Engineering Division Meeting August 18, 2010.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Content The system development life cycle
Team Think For You. Outline  Introduction  Process  Requirements Engineering  Architecture  Detailed Design  Testing  Demo  Extensibility  Conclusions.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Team Skill 6: Building the Right System Assessing Requirements Quality (29)
INFORMATION X INFO425: Systems Design Systems Design Project Deliverable 1.
January 24, 2009 Agile Product Management Making Things Happen Walter Bodwell Planigle.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
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.
Stages of design  High level design  High level data structure  Architecture  Low level design-code design  Algorithms  Low level data structures.
#2-What is Agile? Why Agile? Subtopics 1- Agile motivation for software / systems 2- Agile tenets and principles 3- Agile as a risk mitigation strategy.
#7-Effect of Agile on Post-Contract Award Subtopics #1- Documentation #2- Regulatory oversight #3- Participating in Agile reviews #4- Measurement ELO ELO.
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.
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.
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
#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.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Project Management Enabling Quality Marien de Wilde, PMP April 2007.
Technical Operations 12 th July 2010 Dr Phil Spiby Eurostep Limited Integrating Systems Engineering Information with AP233.
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.
3-Basic Agile Concepts Subtopics 1-The agile methods landscape 2-Common agile concepts and practices 3-Differences between traditional development and.
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
Module 1 Review of Data Collection and Analysis Concepts
DoD Cyberspace Workforce Definitions
CLE Introduction to Agile Software Acquisition
CLE Introduction to Agile Software Acquisition
#2-What is Agile? Why Agile?
The Open Group Architecture Framework (TOGAF)
Defense Business Systems (CLE077) Sprint
DoD Cyberspace Workforce Definitions
Resources & References on Agile Methodologies
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Some Practical Considerations for Systems Engineers in a Lean-Agile Airborne Weapons System Program June 12, 2018 Ken Garlington.
Agile Development – a new way of software development?
Adapting Agile in Pharmaceutical Industries
System Development Methods
Presentation transcript:

Module 5: Effect of Agile on Engineering & Test Staff TLO: Given a DoD program involved in software development using Agile IPM methodologies, the student will understand differences in engineering and test roles to enable program success. ELOs 1.Identify how program technical requirements are managed in Agile contracting settings 2.Identify how program baselines are managed in an Agile environment 3.Recognize key factors for developmental testing success in an Agile environment 4.Identify different ways that System Engineering Technical processes interact with Agile Software approaches CLE Introduction to Agile Software Acquisition1 Assessment LP - In Agile settings, low level requirements add who and why to the typical what of requirements, often using a format called a “story” (ELO 1) LP - Requirements in an Agile contracting setting need to be prioritized in terms of the rank order of their value to the end user and other stakeholders (ELO 1) MT - A requirements baseline that is at too low a level of abstraction is unproductive for an Agile contract setting (ELO 1) MT - 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 (ELO 1) MT - automated testing is a necessity, not an option, for any decent-sized Agile program (ELO 3)

CLE Introduction to Agile Software Acquisition2 Module Contents 1 - Systems Engineering – Requirements (ELO 1, 2) 2 - Systems Engineering – Technical Processes (ELO 2) 3 - Integration and Testing (ELO 3) Module Story What story do we want to tell as motivation and to support terminal learning objective

Subtopic 1: Systems Engineering - Requirements Requirements and Configuration Management Flow of expressing requirements (somewhat of a review from Module 4) Using a user story to flesh out details of requirements Horizontal and vertical traceability Flow and configuration management of requirements, prioritization and releases Major Takeaways A requirements baseline that is at too low a level of abstraction is unproductive for an Agile contract setting. In Agile settings, low level requirements add who and why to the typical what of requirements, often using a format called a “story” 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 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. CLE Introduction to Agile Software Acquisition3

Suggested Content CLE Introduction to Agile Software Acquisition4

Suggested Content CLE Introduction to Agile Software Acquisition5

Subtopic 2: Systems Engineering – Technical Processes Approaches to managing interaction with Agile Software teams Systems Engineers Acting as Agile Product Owner Systems Engineers Acting as Agile Systems Architect Systems Engineers Applying Agile Methods to Their Own Work Program baselines in an Agile setting (needs major work) Technical reviews that establish and evolve program baselines Functional, Allocated, Product Resource: Lean Engineering reference CLE Introduction to Agile Software Acquisition6

Suggested Content CLE Introduction to Agile Software Acquisition7

Suggested Content CLE Introduction to Agile Software Acquisition8

Subtopic 3: Integration and Testing Use of supplemental test strategy to compliment the high level program TEMP Deal with Measures of Effectiveness for traceability Integration approaches for DT/OT activities Developmental testing and evaluation in an iterative approach Cybersecurity staff involvement Ensuring integrity of the definition of done – including cyber Leverage multiple sources of evidence (unit testing, demos, traditional system testing) Automated testing and automation support Major Takeaways automated testing is a necessity, not an option, for any decent-sized Agile program CLE Introduction to Agile Software Acquisition9

Suggested Content—Need for Reaccreditation CLE Introduction to Agile Software Acquisition10

Suggested Content—Cybersecurity recommendations CLE Introduction to Agile Software Acquisition11