Agile Systems Engineering: What is it and What Have We Learned?
|
|
- Arthur Stevenson
- 2 years ago
- Views:
Transcription
1 Agile Systems Engineering: What is it and What Have We Learned? March 2012 Dr. Suzette S. Johnson Agile Engineering Northrop Grumman
2 Getting To Know You! Dr. Suzette Johnson Northrop Grumman Agile Community of Practice Chair Champion of Agile practices across NGC ADAPT Executive Committee (Industry working group) As a systems engineer, project manager, and certified Scrum Professional, with an interest and passion for promoting and implementing Agile practices in largescale systems environments. Provides coaching, consulting, mentoring, training, etc. for Northrop Grumman programs Lean and Agile experience started in 1999 Dissertation focused on investigating the impact of leadership styles on software project outcomes in traditional and agile engineering environments 2
3 Discussion Outline Defining an Agile Environment and Agile Systems Engineering (ASE) Requirements, Use Cases, User Stories Levels Planning User Story Verification and Validation Summary References 3
4 ASE: What Have We Learned About? Systems Engineering and Team Collaboration Evolving Architecture Requirements and Delivering Value Verification and Validation within the Iteration Collaboration and Transparency with Stakeholders 4
5 INCOSE Definition of Systems Engineering Concentrates on the design and application of the whole system It focuses on defining customer needs and required functionality early in the development cycle. Reference: (2011). INCOSE SE Handbook V3.2.1, p /22/2012
6 An Agile Environment Adaptive, Responsive, Evolving, Continuous Improvement Improved transparency of progress End-to-end accountability and ownership Reduces time-to-deploy operational capability Ability to adapt to changing requirements and new technological advancements Agile is an empirical process 6
7 Agile Principles Early and Continuous Delivery of Value A Working System is the Primary Measure of Progress Welcome Changing Requirements Deliver a Working System Frequently Business People and Developers Must Work Together Daily Motivated and Empowered Individuals Face-to-face Conversation Promote Sustainable Development Continuous Attention to Technical Excellence Simplicity The Best Architectures, Requirements and Designs Emerge From Self-Organizing Teams Regular Team Reflection on How to Become More Effective 7
8 INCOSE Says. 8 Reference: (2011). INCOSE SE Handbook V p.40. 3/22/2012 A snippet.
9 NG ISO/IEC/IEEE Based SE Process V-Model Stakeholder Requirements Definition Requirements Analysis Project Processes Project Planning Project Assessment & Control Decision Mgmt Risk Mgmt Configuration Mgmt Information Mgmt Measurement Validation Verification Architectural Design Integration Implementation Technical Processes
10 Our User Story for this Presentation User Story As a Systems Engineer I want to have a better understanding as to how Systems Engineering practices align with the Agile framework so I have insight as to how this might be implemented in an Agile environment. Acceptance Criteria Communicate how requirements analysis and design occur when using an Agile approach Discuss considerations regarding architecture Understanding of the relationship of requirements to user stories and why user stories Insight into the Agile framework and how it helps manage changing requirements and priorities Identification of verification and validation practices within the context of the Agile framework 10 3/22/2012
11 The Agile Scrum Framework Capabilities and User Stories Prioritized by Product Owners The Daily Tasks managed by the Cross Functional Team Design, Code, Integrate, Test Commitment Identification of Impediments Communication Creates the release plan 24 Hours Daily Scrum Meeting Product Backlog Release Plan Iteration Backlog 2-4 Weeks Iteration Feature Demonstration and Retrospective Potentially Shippable Product Increment THIS SIDE UP System Architecture System Design Requirements 1 Inspect and Adapt Visibility and Transparency
12 Lesson Learned 1: Team Collaboration Systems Engineers are part of the Cross-Functional Team with regular collaboration at the team level and across the teams to provide an end-to-end systems view Chief Systems Engineer/Architect becomes more critical as you scale 12 3/22/2012
13 Project Team Structure PM and Technical Lead End-to-End System Capabilities Chief Engineer Chief Architect Quality Cross Functional Team 1 Cross Functional Team 2 Cross Functional Team 3 Cross Functional Team n Progress against end - to - end capabilities Services Supports Cross Functional Teams 13 An Example Network/ Systems Administration Configuration Mgt. Push accountability and ownership to the team level Everyone trained
14 Project Team Structure PM and Technical Lead End-to-End System Capabilities Product Owner Chief Engineer Chief Architect Quality Cross Functional Team 1 Cross Functional Team 2 Cross Functional Team 3 Cross Functional Team n Scrum Master Progress against end - to - end capabilities Developer Developer Integrator Configuration Management Tester Systems Engineer Developer Services Supports Cross Functional Teams Network/ Systems Administration Push accountability and ownership to the team level 14 An Example Configuration Mgt. Everyone trained
15 Project Team Structure Cross Team Collaboration Understanding the bigger picture Systems Engineer Systems Engineer Systems Engineer A Cross-functional team is responsible for capability/thread from planning to final acceptance. Systems Engineers from the teams collaborate to maintain an end-to-end systems view. 15
16 Lesson Learned 2: Architecture Systems Engineering activities provide the context for the development activities (i.e. user stories as part of a systems capability) Architecture development is ongoing (emerging) and focuses on small increments/releases of value Emphasis on a modular architecture with well defined interfaces Iteration 0 (defined timeframe) to define enough of the architecture to get started; model in smaller increments (release/iteration level) Emerging versus Intentional Architecture Regular Architecture Meetings 16 3/22/2012
17 Planning and Estimating the Work Developing Understanding Creating the Vision Agile Systems Engineering: Delivering Value Product Vision Captured Capabilities System Architecture Requirements mapped to stories Revisit architecture and design each release and iteration Use Cases/ Requirements System Level Validations User Stories and Acceptance Tests Architecture Sequence Diagrams Activity Flow Diagrams Product Backlog Functional Non-Functional 6-9 months 1 6 months 1-4 weeks Daily Product Roadmap Release Planning Sprint Planning Daily Plans and Commitment
18 Lesson Learned 3: Requirements Requirement analysis is done during release planning for that release Requirement development and deployment of highest priority capabilities first Every iteration learning from the previous iteration is fed into the next iteration planning and prioritization cycle Uses cases are a tool and provide the greater context for user stories High level requirements are decomposed into a set of user stories User stories convey understanding (user, need, why) and includes acceptance criteria User stories are more than functional requirements 18 3/22/2012
19 Agile Systems Engineering Ontology Simplified view for creating the Product Backlog Requirement Use Case How does this get done? Who s creating the PBL? Epic Stories User Stories (Iteration-Sized) The Product Backlog The list of ranked or prioritized stories to be worked 19 3/22/2012
20 Use Case to Scenario to User Story Use Case 2 One Scenario within the use case 1 3 A user story is a segment of a scenario As a [user/system] I want [what] so that [why]. 20
21 Example Requirement: The hotel reservation system shall enable the user to make room reservations with confirmation of payment. Use Case: Vacation Planner makes hotel room reservation Actor: Vacation Planner Success Guarantee: Room reserved; credit card charged and confirmation received Main Scenario: Search for discounted rooms. Room identified. Save selection. Vacation Planner selects payment type Vacation Planner submits credit card number, expiration date, name. System validates card System charges credit card Confirmation number provided 22 3/22/2012
22 Requirement to User Stories The hotel reservation system shall enable the user to make reservations with confirmation of payment. As a premiere member, I want to search for available discounted rooms. As a vacationer, I want to search for available rooms. As a vacation planner I want to pay for my reservation with a credit card. 23
23 Requirement to User Stories The hotel reservation system shall enable the user to make reservations with confirmation of payment. User Story As a vacation planner I want to pay for my reservation with a credit card so I can confirm my reservation. Acceptance Criteria and Verification Verify: Demonstrate with American Express Demonstrate with Master Card Demonstrate with Visa 24
24 What About Other Types of Requirements? As a vacationer and user of the hotel website, I want the system to be available 99.99% of the time As a vacationer, I want web pages to download in <4 seconds Non-functional requirements Performance requirements Constraints As the hotel website owner, I want 10,000 concurrent users to be able to access the site at the same time with no impact to performance Describes system behavior or characteristics 25 Reference: Mike Cohn, mountaingoatsoftware.com
25 Product Vision and Roadmap Release 1 Release 2 Release 3 Release 4 March 31, 2012 June 30, 2012 Sept. 30, 2012 Dec. 20, 2012 Room reservations and payment User profiles for future visits Hotel amenities Conference offerings Online chat support Local information Special discounts for room reservations Improve usability Google maps Air and hotel package deal Meeting and Business plans and reservations Longer term planning High level capabilities (sometimes written as goals) 26
26 Release Plan, Iteration Plan, Daily Plan Example: Hotel Website Requirement 1: The hotel reservation system shall allow the user to make reservations. 27 Release Plan (Set of User Stories) User Stories As a vacationer, I want to search room availability As a vacationer, I want to save my request As a vacationer, I want to pay with a credit card Demonstrate with search on 1 room Demonstrate with search on executive suite. Points 12 Demonstrate. 8 Demonstrate 21 Iteration Plan (User Stories with Tasks) Hours Design Review 4 Install Baseline 4 Documentation 8 Acquire Test Data 8 Code 24 Develop Tests 8 Run Tests 8 Detailed planning saved to the last responsible moment The Daily Plan Yesterday I started on the interface. Today I plan to The one thing standing in my way What about the System Engineering? 1. User Stories 2. Tasks under a User Story 3. Preparing for the next iteration
27 Lesson Learned 4: Validation and Verification Validation is an important function of the iteration Occurring at the beginning and the end Testing is defined before development for the release/iteration begins Testers collaborate daily as part of the Cross Functional Team 28
28 The Agile Framework Capabilities and User Stories Prioritized by Product Owners Creates the release plan Product Backlog The Daily Tasks managed by the Cross Functional Team Release Plan Iteration Backlog Design, Code, Integrate, Test 24 Hours 2-4 Weeks Iteration Commitment Identification of Impediments Verification Some independent testing Daily Scrum Meeting Communication Feature Demonstration and Retrospective Validation Potentially Shippable Product Increment THIS SIDE UP 2 Validation Inspect and Adapt Visibility and Transparency How do you define release?
29 Iteration Demonstration and Acceptance Transparency and information sharing Team presents what it accomplished during the iteration Typically takes the form of a demo of new features or underlying architecture Time-boxed Whole team participates Feedback from stakeholders and users User Stories validated and accepted Metrics updated User Story Validation 30
30 Requirements Mapping Requirement to story mapping Requirement to Story to Test to Verification Inspection Updated each iteration 32
31 Lesson Learned 5: Transparency Regular engagement with the users and customer is imperative Ongoing collaboration and transparency are critical for mission success 33 3/22/2012
32 Final Notes Requirements Analysis and Design Upfront requirement analysis is done during release planning for that release Uses cases are a tool and provide the greater context for user stories Architecture and initial design are first developed during iteration/release 0 Every iteration the team determines if a design review is needed Requirements and User Stories High level requirements are decomposed into a set of user stories User stories convey understanding (user, need, why) User stories create the Product Backlog Validation and Verification High level requirements have tests and each user story has tests. Validation begins with the release planning phase and occurs again during the iteration boundaries Each story has acceptance criteria that is defined before the release/iteration begins Requirements Traceability/Verification Matrix is updated each iteration 34
33 Checkpoint: Our User Story User Story As a Systems Engineer I want to have a better understanding as to how Systems Engineering practices align with the Agile framework so I have insight as to how this might be implemented in an Agile environment. Acceptance Criteria Communicate how requirements analysis and design occur when using an Agile approach Discuss considerations regarding architecture Understanding of the relationship of requirements to user stories and why user stories Insight into the Agile framework and how it helps manage changing requirements and priorities Identification of verification and validation practices within the context of the Agile framework 35 3/22/2012
34 References and Recommended Readings Agile Requirements and Collaboration Requirements by Collaboration Collaboration Explained Ellen Gottesdiener, EBG Consulting Jean Tabaka, Rally Software User Stories Applied Mike Cohn Agile Development Practices Agile Software Requirements Agile Software Development with Scrum Dean Leffingwell Ken Schwaber and Mike Beedle Agile Testing Lisa Crispin and Janet Gregory Agile Estimating and Planning Agile Modeling Mike Cohn Scott Ambler 36
35 INCOSE References The INCOSE SE Handbook V3.2.1 states: INCOSE use: Permission to reproduce and use this document or parts thereof by members of INCOSE and to prepare derivative works from this document for INCOSE use is granted, with attribution to INCOSE and the original author(s) where practical, provided this copyright notice is included with all reproductions and derivative works. Content from ISO/IEC 15288:2002 and 15288:2008 is used by permission, and is not to be reproduced other than as part of this total document. Reference: (2011). INCOSE SE Handbook V p.ii. 37 3/22/2012
36 38 3/22/2012
T14 "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development BIO PRESENTATION 6/21/2007 1:30:00 PM
BIO PRESENTATION T14 6/21/2007 1:30:00 PM "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development Better Software Conference & EXPO June 18-21, 2007 Las Vegas, NV USA
Agile Software and Systems Engineering Tutorial
Agile Software and Systems Engineering Tutorial Systems and Software Technology Conference Salt Lake City, UT April 2010 John O. Clark Chief Engineer Northrop Grumman Virginia Beach, VA Dr. Suzette S.
Agile Project Management By Mark C. Layton
Agile Project Management By Mark C. Layton Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products. Agile project management
ScrumMaster Certification Workshop: Preparatory Reading
A S P E S D L C Tr a i n i n g ScrumMaster Certification Workshop: Preparatory Reading A WHITE PAPER PROVIDED BY ASPE ScrumMaster Certification Workshop: Preparatory Reading Greetings, Potential Certified
Bridging the Gap Between Acceptance Criteria and Definition of Done
Bridging the Gap Between Acceptance Criteria and Definition of Done Sowmya Purushotham, Amith Pulla sowmya.sudha@gmail.com, amith.pulla@intel.com Abstract With the onset of Scrum and as many organizations
D25-2. Agile and Scrum Introduction
D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of
Scrum Guidelines. v.2 2011 W W W. S C R U M D E S K. C O M
Scrum Guidelines v.2 2011 W W W. S C R U M D E S K. C O M WHY Agile Ceremonies Agile project is developed in repeatable ceremonies that give rhythm to delivery. Product Strategy Once per year Release Planning
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization
SESSION 303 Wednesday, March 25, 3:00 PM - 4:00 PM Track: Support Center Optimization Secrets of a Scrum Master: Agile Practices for the Service Desk Donna Knapp Curriculum Development Manager, ITSM Academy
Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT
Jukka Mannila KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT Information Technology 2013 KEY PERFORFORMANCE INDICATORS IN AGILE SOFTWARE DEVELOPMENT Mannila, Jukka Satakunnan ammattikorkeakoulu,
Introduction to Agile Scrum
Introduction to Agile Scrum by Julia M. Lobur Penn State Harrisburg CMPSC 487W Fall 2015 Introduction to Scrum Learning Goals Relationship of Scrum to other Agile methods Scrum Framework Scrum Roles Scrum
Scrum. SE Presentation. Anurag Dodeja Spring 2010
Scrum SE Presentation by Anurag Dodeja Spring 2010 What is Scrum? Scrum is an agile software development framework. Work is structured in cycles of work called sprints, iterations of work that are typically
The Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
Testing in an Agile Environment Understanding Testing role and techniques in an Agile development environment. Just enough, just in time!
Testing in an Agile Environment Understanding Testing role and techniques in an Agile development environment. Just enough, just in time! Today s Topics How the Tester s Role Changes in Agile Testing in
Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012
Scrum and Testing The end of the test role Bryan Bakker 20 maart 2012 voordracht georganiseerd door Discussiegroep Software Testing met de steun van Ingenieurshuis, Antwerpen Scrum and Testing... The end
Agile Software Engineering: Interactive Workshop
Agile Software Engineering: Interactive Workshop IEEE Software Technology Conference Long Beach, CA March 31, 2014 Steven Baynes Agile Engineering Northrop Grumman Steven.Baynes@ngc.com Copyright 2014
AGILE - QUICK GUIDE AGILE - PRIMER
AGILE - QUICK GUIDE http://www.tutorialspoint.com/agile/agile_quick_guide.htm Copyright tutorialspoint.com AGILE - PRIMER Agile is a software development methodology to build a software incrementally using
Introduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014 1 Goals Cover Material from our User Stories Book Chapter 15: Using Stories With Scrum Chapter 16: Additional
SCRUM BODY OF KNOWLEDGE (SBOK Guide)
A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK Guide) 2013 Edition A Comprehensive Guide to Deliver Projects using Scrum TABLE OF CONTENTS TABLE OF CONTENTS 1. INTRODUCTION... 1 1.1 Overview of Scrum...
PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan
PLM - Agile Agile Development Evolved in the 1990s as a response to heavyweight methodologies. In 2001 representatives of various new methodologies met to discuss the need for lighter alternatives. The
Agile Software Development. Stefan Balbo / Patrick Dolemieux
Agile Software Development Stefan Balbo / Patrick Dolemieux Agile Software Development Stefan Balbo / Patrick Dolemieux Content Why go Agile? Introduction to Scrum - Process - Roles Agile Estimating and
Course Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
Agile Scrum and PMBOK Compatible or Contrary?
Agile Scrum and PMBOK Compatible or Contrary? Paul Despres PMI Emerald Coast Panama City Branch June 26, 2014 Meeting Overview Agenda Topics: Review Agile/Scrum Methods Review PMBOK Structure Demonstrate
What is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process
What is Scrum? From http://www.scrumalliance.org/pages/what_is_scrum A lean approach to software development Scrum is an agile software development framework. Work is structured in cycles of work called
Glossary SAFe 4.0 for Lean Software and Systems Engineering
Agile Architecture Agile architecture is a set of values and practices that support the active evolution of the design and architecture of a system, concurrent with the implementation of new business functionality.
Enchantment Chapter Monthly Meeting
Enchantment Chapter Monthly Meeting 10 June, 2015 4:45-6:00 pm: Systems Engineering for Software Intensive Projects using Agile Methods Larri Rosser, Raytheon Intelligence, Information & Services, Sr.
Systems Engineering for Software Intensive Projects Using Agile Methods
Systems Engineering for Software Intensive Projects Using Agile Methods Larri Rosser Raytheon Intelligence, Information and Services Garland, TX larri_rosser@raytheon.com Phyllis Marbach Boeing Huntington
Agile Software Development in the Large
Agile Software Development in the Large Jutta Eckstein 1 Large Large in... Scope Time People Money Risks We concentrate on Large Teams Large is relative 1, 2, 10, 100, 2000 People 2 Principles behind Agile
2015 Defense Health Information Technology Symposium Implementation of Agile SCRUM Software Development Methodology
Mr. Christopher Harrington, PM Clinical Support, Solution Delivery Division Mr. James Huber, Healthcare Data Analyst, DHA Decision Support 2015 Defense Health Information Technology Symposium Implementation
Roles: Scrum Master & Project Manager
Roles: Scrum Master & Project Manager Scrum Master: Facilitate collaborative meetings Track team performance Remove impediments (Risk, Issue) Validate team alignment to Agile framework and scope Drive
Creating and Maintaining the Product Backlog
Creating and Maintaining the Product Backlog Presented by: In partnership with: 1 Josh Fruit Agile Coach & Trainer Davisbase Consulting Background in Development with 6 years IT Management leading cross-functional
Executive Guide to SAFe 24 July 2014. An Executive s Guide to the Scaled Agile Framework. alshall@netobjectives.com @AlShalloway
An Executive s Guide to the Scaled Agile Framework Al Shalloway CEO, Net Objectives Al Shalloway CEO, Founder alshall@netobjectives.com @AlShalloway co-founder of Lean-Systems Society co-founder Lean-Kanban
Scrum. The Essence. Tobias Mayer, http://agilethinking.net. Sonntag, 19. Februar 12
Scrum The Essence What is Scrum? Scrum is a framework that allows you to create your own lightweight process for developing new products. Scrum is simple. It can be understood and implemented in a few
Capstone Agile Model (CAM)
Capstone Agile Model (CAM) Capstone Agile Model (CAM) Approach Everything we do within the Capstone Agile Model promotes a disciplined project leadership process that encourages frequent inspection and
SECC Agile Foundation Certificate Examination Handbook
Versions 2.0 Version Date Remarks 1.0 12/4/2012 Initial version 2.0 3/8/2008 REVISION HISTORY Updated knowledge areas Added questions examples Updated suggested readings section Page 2 of 15 Version 2.0
Introduction to Enterprise Agile Frameworks
Introduction to Enterprise Agile Frameworks PMINU PDC 2014 May 9, 2014, Salt Lake City, Utah Presented by: Mehul Kapadia SAFe SPC, PMI-ACP, CSM, CSPO, PMP 1 Introduction Mehul Kapadia Director of Project
Learn. Inspect. Adapt: An Overview of Agile Project Delivery. Doug Rosenberg and Kara Silva June 19, 2008
Learn. Inspect. Adapt: An Overview of Agile Project Delivery Doug Rosenberg and Kara Silva June 19, 2008 Paper Airplanes! The Agile Manifesto We are uncovering better ways of developing software by doing
Practical Agile Requirements Engineering
Defense, Space & Security Lean-Agile Software Practical Agile Requirements Engineering Presented to the 13 th Annual Systems Engineering Conference 10/25/2010 10/28/2010 Hyatt Regency Mission Bay, San
SCALING AGILE. minutes
SCALING AGILE in 5 minutes THREE AGILE COMPANIES Basement Apps Ltd is having unexpected success with a social media app for musicians. Software Supply Ltd needs more diverse development teams as the company
Maximize Benefits of Agile Practices
Maximize Benefits of Agile Practices January 2016 Author: Dr. Tonya M. Peterson, PMP, CSM 2 Agile Manifesto 3 A good entrepreneur has a very clear grasp of what the goal is, an unwavering sense of the
Getting Agile with Scrum. We re losing the relay race
Getting Agile with Scrum Mike Cohn 6 June 2014 1 We re losing the relay race The relay race approach to product development may conflict with the goals of maximum speed and flexibility. Instead a holistic
Adapting Agile Software Development to Regulated Industry. Paul Buckley Section 706 Section Event June 16, 2015
Adapting Agile Software Development to Regulated Industry Paul Buckley Section 706 Section Event June 16, 2015 Agenda FDA s expectations for Software Development What is Agile development? Aligning Agile
Introduction to Agile Practices
Introduction to Agile Practices Phyllis Marbach, INCOSE Agile Systems & Systems Engineering Working Group February 2, 2016 INCOSE INSIGHT July 2014 1 Current State of Intelligent Transportation Systems
Answered: PMs Most Common Agile Questions
Answered: PMs Most Common Agile Questions Mark Kilby Agile Coach, Rally Software mkilby@rallydev.com 407.687.3350 (cell) Led Fortune 50 agile transitions in - Government - Technology - Healthcare - Insurance/Fina
Agile Project Management Mapping the PMBOK Guide to Agile Practices. Michele Sliger michele@sligerconsulting.com Twitter: @michelesliger
Agile Project Management Mapping the PMBOK Guide to Agile Practices Michele Sliger michele@sligerconsulting.com Twitter: @michelesliger Michele Sliger Sliger Consulting, Inc. www.sligerconsulting.com Over
The Truth About Agile Software Development with Scrum, The Facts You Should Know
The Truth About Agile Software Development with Scrum, The Facts You Should Know Copyright Notice of rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any
Agile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 4 Scrum: Current Framework 1 Scrum: New Process Framework 1. A people-centric framework based on a set of values, principles, and practices that
Mastering the Iteration: An Agile White Paper
Rally Software Development Corporation Whitepaper Mastering the Iteration: An Agile White Paper Dean Leffingwell Abstract: The heartbeat of Agile development is the iteration the ability of the team to
Scaling Agile: Fractals of Innovation. An excerpt from Rally s book, Agile Business Rally Software Development Corp. All rights reserved.
Scaling Agile: Fractals of Innovation An excerpt from Rally s book, Agile Business 2013 Rally Software Development Corp. All rights reserved. Scaling Agile: Fractals of Innovation By Ronica Roth Sure,
04 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Agile Quick Facts AGILE PRINCIPLES Customer Satisfaction 01 Changing Requirements 02 Frequent Delivery 03 Collaboration 04 Our highest priority is to satisfy the customer through early and continuous delivery
CSSE 372 Software Project Management: More Agile Project Management
CSSE 372 Software Project Management: More Agile Project Management Shawn Bohner Office: Moench Room F212 Phone: (812) 877-8685 Email: bohner@rose-hulman.edu Learning Outcomes: Plan Create a plan for
Agile & PMI Project Management Mapping MAVERIC S POINT OF VIEW. 10-10-2012 Vol. 7
10-10-2012 Vol. 7 MAVERIC S POINT OF VIEW Agile & Abstract: The purpose of this whitepaper is to explore the points of parity and differences between two of the most widely used methodologies. PMI Management
Course Title: Planning and Managing Agile Projects
Course Title: Planning and Managing Agile Projects Course ID: BA15 Credits: 21 PDUs Course Duration: 3 days (Live in person class only) Course Level: Basic/Intermediate Course Description: This 3-day course
Agile Metrics. It s Not All That Complicated
Agile Metrics It s Not All That Complicated Welcome About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach Certified Scrum Master Certified Scrum Product Owner Led teams/org s to
CSPO Learning Objectives Preamble. Scrum Basics
CSPO Learning Objectives Preamble This document contains topics for the Certified Scrum Product Owner (CSPO) training course. The purpose of this document is to describe the minimum set of concepts and
Sometimes: 16 % Often: 13 % Always: 7 %
SCRUM AT RIIS A Standish study found that only 20% of features in a typical system were used often or always and 45% of features were never used at all. The ability to embrace change is critical to reducing
copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner s Approach, 6/e Chapter 4 Agile Development copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use
Waterfall to Agile. DFI Case Study By Nick Van, PMP
Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall
A Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com)
A Viable Systems Engineering Approach Presented by: Dick Carlson (richard.carlson2@boeing.com) Philip Matuzic (philip.j.matuzic@boeing.com) i i Introduction This presentation ti addresses systems engineering
LEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
An Introduction to Scrum
An Introduction to Scrum CS 451 Software Engineering Scrum in 100 words Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. It allows us to
Agile Requirements by Collaboration
Agile Requirements by Collaboration [Aarhus, DK; 5 October 2010] Ellen Gottesdiener www.ebgconsulting.com Ellen Gottesdiener Founder & Principal Consultant, EBG Consulting Facilitator, trainer, mentor,
Using Scrum to Streamline Web Applications Development and Improve Transparency. Michelle Frisque
Using Scrum to Streamline Web Applications Development and Improve Transparency Michelle Frisque September 2010 OVERVIEW! Background! The problem! The proposed solutions:! Creation of Web Committee! Implementing
Agile Project. Management FOR DUMME&* by Mark C. Layton WILEY. John Wiley & Sons, Inc.
Agile Project Management FOR DUMME&* by Mark C. Layton WILEY John Wiley & Sons, Inc. Table of Contents»#» « Introduction / About This Book 1 Foolish Assumptions 1 Conventions Used in This Book 2 How This
CS435: Introduction to Software Engineering! " Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman
CS435: Introduction to Software Engineering! " " " " " " " "Dr. M. Zhu! Chapter 3! Agile Development! Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman
The Agile Manifesto is based on 12 principles:
The Agile Manifesto is based on 12 principles: Customer satisfaction by rapid delivery of a useful product solution Welcome changing requirements, even late in development Working products are delivered
Secrets of a Scrum Master: Agile Practices for the Service Desk
Secrets of a Scrum Master: Agile Practices for the Service Desk #askitsm @ITSMAcademy @ITSM_Lisa @ITSM_Donna ITSM Academy About ITSM Academy NextGen ITSM Education: Certified Process Design Engineer (CPDE)
Water-Scrum-Fall Agile Reality for Large Organisations. By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com
Water-Scrum-Fall Agile Reality for Large Organisations By Manav Mehan Principal Agile consultant Manav.Mehan@tcs.com Interests and Experience Leading Change and Transformation in Large, Complex organisations
Agile Scrum Workshop
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
GAO Scheduling Best Practices Applied to an Agile Setting
GAO Scheduling Best Practices Applied to an Agile Setting by Juana Collymore and Brian Bothwell April 15, 2015 Outline Why is scheduling important? GAO Schedule Assessment Guide Overview Status of the
The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July 2013. Developed and sustained by Ken Schwaber and Jeff Sutherland
The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game July 2013 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide... 3 Definition of
Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
Scaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London 2007. conchango 2007 www.conchango.com
Scaling Scrum Colin Bird & Rachel Davies Scrum Gathering London 2007 Scrum on a Slide Does Scrum Scale? Ok, so Scrum is great for a small team but what happens when you have to work on a big project? Large
26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: 224-595-8846 AGILE THROUGH SCRUM
26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: 224-595-8846 AGILE THROUGH SCRUM 1 AGENDA & LEARNING POINTS 1. Open 2. Agile Overview 3. Scrum Basics Learning
CSSE 372 Software Project Management: Managing Agile Projects
CSSE 372 Software Project Management: Managing Agile Projects Shawn Bohner Office: Moench Room F212 Phone: (812) 877-8685 Email: bohner@rose-hulman.edu XKCD Reference Learning Outcomes: Plan Create a plan
Effective Release Management in Agile Scrum methodology. Submitted to. The Project Management Leadership Conference 2006 QAI India Pvt. Ltd.
Page 1 of 12 Effective Release Management in Agile Scrum methodology Submitted to The Project Management Leadership Conference 2006 QAI India Pvt. Ltd. Authors: A Narasimhan a.narasimhan@siemens.com Niladri
Introduction... 2 Introducing the DSDM Agile Project Framework (AgilePF)...2 Introducing DSDM...2 Introducing Scrum...3
Contents Introduction... 2 Introducing the DSDM Agile Project Framework (AgilePF)...2 Introducing DSDM...2 Introducing Scrum...3 AgilePF for Scrum... 4 Philosophy...4 Agile Values...4 Principles...5 Variables...8
Neglecting Agile Principles and Practices: A Case Study
Neglecting Agile Principles and Practices: A Case Study Patrícia Vilain Departament de Informatics and Statistics (INE) Federal University of Santa Catarina Florianópolis, Brazil vilain@inf.ufsc.br Alexandre
Agile Development and Software Architecture: Understanding Scale and Risk
Agile Development and Software Architecture: Understanding Scale and Risk Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Robert L. Nord SSTC, April 2012 In collaboration
Agile Software Development with Scrum. Jeff Sutherland Gabrielle Benefield
Agile Software Development with Scrum Jeff Sutherland Gabrielle Benefield Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise:
Agile in Financial Services A Framework in Focus
Agile in Financial Services A Framework in Focus John B. Hudson, B.Sc, PMP, CSM PMI NJ Chapter February 19, 2013 19 Feb 2013 1 Objectives 1. Agile Development an Overview 2. The Agile Enterprise Infrastructure
As the use of agile approaches
What Does a Business Analyst Do on an Agile Project? By Kent J. McDonald Senior Instructor, B2T Training As the use of agile approaches increases, business analysts struggle to determine how their role
Agile Project Management with Scrum
Agile Project Management with Scrum Resource links http://www.agilealliance.org/ http://www.agilemanifesto.org/ http://www.scrum-master.com/ 1 Manifesto for Agile Software Development Individuals and interactions
Terry Fischer Is Agile Scrum the Right Methodology for Your BI Project? Session 3504
Terry Fischer Is Agile Scrum the Right Methodology for Your BI Project? Session 3504 LEARNING POINTS What is the Agile Scrum and for what types of projects is it best utilized? How to apply general Agile
Agile Project Management
Agile Project Management Projekt-Kick-Off-Tage Hochschule Augsburg Martin Wagner, 15. März 2011 TNG Technology Consulting GmbH, http://www.tngtech.com Agile project management with Scrum Agenda Software
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Each percentage
RISK MANAGMENT ON AN AGILE PROJECT
BIO PRESENTATION W3 6/28/ 11:30 AM RISK MANAGMENT ON AN AGILE PROJECT Michele Sliger Rally Software Development Better Software Conference June 26 29, Las Vegas, NV USA Michele Sliger Michele Sliger has
Atomate Development Process. Quick Guide
Development Process Quick Guide METHODOLOGY Every project is unique You know your business inside out. You have thought and planned your ideas carefully and are keen to see it live as soon as possible.
Introduction to Scrum for Managers and Executives
Introduction to for Managers and Executives goodagile> Certified Training and Consulting in India and Asia www.goodagile.com The Problems Many Companies Face Time-to-market for products is too long Project
Agile Software Development
Agile Software Development Application in the Medical Device Industry Kelly Weyrauch Medtronic, Inc. (29 April 2008) Introduction Purpose Provide an introduction to Agile Software Development as it applies
BEDIFFERENT ACE G E R M A N Y. aras.com. Copyright 2012 Aras. All Rights Reserved.
BEDIFFERENT ACE G E R M A N Y ACE Germany Implementation Best Practices Scrum Methodology Patrick Willemsen Senior Consultant ARAS Software AG Slide 3 Dilbert says Slide 4 Agenda Agile Methodology An Overview
Your Agile Team s Indispensible Asset
Agile / Scrum Training Lean Software Development Agile Organizational Metrics Executive Coaching Improved Team Dynamics Improved Efficiency! Your Agile Team s Indispensible Asset The Agile Business Analyst
USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell
USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015 Dr. Patrick McConnell July 9, 2015 1 First, an old joke.. I can t identify an original source for this cartoon. As best as I can tell, the art
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Total questions
Agile Software Engineering Practice to Improve Project Success
Agile Software Engineering Practice to Improve Project Success Dietmar Winkler Vienna University of Technology Institute of Software Technology and Interactive Systems dietmar.winkler@qse.ifs.tuwien.ac.at
PMI Agile Certified Practitioner (PMI ACP) Boot Camp Course AG05; 4 Days, Instructor-led
PMI Agile Certified Practitioner (PMI ACP) Boot Camp Course AG05; 4 Days, Instructor-led Course Description Take this PMI ACP training course to prepare for your Agile Certified Practitioner (PMI ACP)
Development. Lecture 3
Software Process in Modern Software Development Lecture 3 Software Engineering i Practice Software engineering practice is a broad array of principles, concepts, methods, and tools that must be considered
Mike Cohn - background
Scrum for Video Game Development 1 Mike Cohn - background 2 What is Scrum? One of the agile processes Iterative and incremental Produces demonstrable working software every two to four weeks Results- and
Scrum Guide. By Ken Schwaber, May, 2009
Scrum Guide By Ken Schwaber, May, 2009 Scrum has been used to develop complex products since the early 1990s. This paper describes how to use Scrum to build products. Scrum is not a process or a technique