Portfolio Management In An Agile World
|
|
- Adrian Burke
- 6 years ago
- Views:
Transcription
1 Portfolio Management In An Agile World Rick Austin VP, Enterprise Engagements Principal @GoAgileCamp #AgileCamp2017
2 2 RICK AUSTIN Information Technology Director Director of Development ABOUT ME Experience applying agile to small teams, large distributed teams, & change management Expert in Financial Services Industry Georgia State Grad Agile Transition Director, Program Manager Agile Project Management Volunteer and Leader Applications Development Manager twitter.com/rickaustin facebook.com/leadingagile linkedin.com/in/rickdaustin
3 3 WHAT ARE WE EXPLORING Using portfolio management so we focus on the most valuable things Balancing capacity against demand How be adaptive and support continuous improvement How to support corporate governance (security, audit etc.)
4 DEFINE PORTFOLIO MANAGEMENT 4 PMI S DEFINITION Portfolio management ensures that an organization can leverage its project selection and execution success. It refers to the centralized management of one or more project portfolios to achieve strategic objectives. Our research has shown that portfolio management is a way to bridge the gap between strategy and implementation.
5 DEFINE PORTFOLIO MANAGEMENT 5 PMI S DEFINITION Portfolio management ensures that an organization can leverage its project selection and execution success. It refers to the centralized management of one or more project portfolios to achieve strategic objectives. Our research has shown that portfolio management is a way to bridge the gap between strategy and implementation. INVESTOPEDIA S DEFINITION Portfolio management is the art and science of making decisions about investment mix and policy, matching investments to objectives, asset allocation for individuals and institutions, and balancing risk against performance.
6 WHAT IS AN AGILE WORLD?
7 7 WHAT DO I MEAN? BACKLOGS TEAMS WORKING TESTED SOFTWARE Defines capabilities to build Small enough for the team to develop in a few days Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt
8 8 WHY ARE THEY IMPORTANT? CLARITY ACCOUNTABILITY MEASURABLE PROGRESS People have clarity around what to build People understand how it maps to the big picture Teams can be held accountable for delivery No indeterminate work piling up at the end of the project
9 9 HOW DOES IT SCALE? GOVERNANCE STRUCTURE METRICS Governance is the way we make economic tradeoffs in the face of constraints They way we form teams and foster collaboration at all levels of the organization What do we measure, how do we baseline performance and show improvement?
10 STRUCTURE
11 11 PORTFOLIO TEAMS PROGRAM TEAMS DELIVERY TEAMS
12 GOVERNANCE
13 13 PORTFOLIO TEAMS PROGRAM TEAMS DELIVERY TEAMS
14 14 PORTFOLIO TEAMS Kanban PROGRAM TEAMS Kanban DELIVERY TEAMS Scrum
15 METRICS
16 16 PORTFOLIO TEAMS Kanban PROGRAM TEAMS Kanban DELIVERY TEAMS Scrum
17 17 PORTFOLIO TEAMS Kanban PROGRAM TEAMS Kanban Backlog Size Velocity Burndown Escaped Defects Commit % Acceptance % Ratio Scope Change DELIVERY TEAMS Scrum
18 18 PORTFOLIO TEAMS Kanban PROGRAM TEAMS Kanban DELIVERY TEAMS Cycle Time Features Blocked Rework/Defects Scrum Backlog Size Velocity Burndown Escaped Defects Commit % Acceptance % Ratio Scope Change
19 19 Takt Time/ Cycle Time Time/Cost/Scope/Value ROI/Capitalization PORTFOLIO TEAMS Kanban PROGRAM TEAMS Kanban DELIVERY TEAMS Cycle Time Features Blocked Rework/Defects Scrum Backlog Size Velocity Burndown Escaped Defects Commit % Acceptance % Ratio Scope Change
20 GOVERNANCE FLOW
21 21 GOVERNANCE Governance is the method for planning, coordinating and tracking requirements. Agile requirements are progressively elaborated from Epics, to Features and finally Stories. FEATURE USER STORY A measurable goal intended to deliver on the intent of an Initiative. Epics are defined and validated by Core Product Teams. A new or improved capability of the system. Features deliver a package of functionality that end users would generally expect to get all at once. Stories are small outcomes designed, built, tested, and delivered in 3-5 days. Stories are elaborated collaboratively between Delivery and Program Teams.
22 22 PORTFOLIO MANAGEMENT STRATEGIC ALIGNMENT DEMAND MANAGEMENT DETAILED PLANNING EXECUTION GOVERNANCE MEASURE EFFECTIVENESS Maximize Strategic Alignment Increase Transparency Organizational focus on delivering the most valuable work Increase predictability Reduce Time to ROI Identify and plan for dependencies Balance capacity and demand Reduce rework Improve quality Agree to minimal capabilities needed to deliver value Ensure credible release planning Assess and guide the progress of value delivery Minimize delivery risks Continually make continue, pivot, kill, ship decisions Revisit business case Validate fitness function for capability
23 23 GOVERNANCE PORTFOLIO TEAM PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION COMPLETED Epic Kanban DEFINITION (DEPENDENCIES, SIZING & RISKS) DEMAND PLANNING & RELEASE ROADMAP MEASURABLE PROGRESS PROGRAM TEAM Feature Kanban PROGRAM WORK INTAKE SOLUTION DESIGN RELEASE PLANNING FEATURE READY IN PROGRESS FEATURE VALIDATION COMPLETED DETAILED PLANNING (CLARITY & VIABILITY) EXECUTION & ACCOUNTABILITY DELIVERY TEAM Story Scrum MAKE READY STORY READY IN PROGRESS STORY DONE STORY ACCEPTED PORTFOLIO PLANNING RELEASE PLAN & DEFINE EXECUTE OPERATE
24 PORTFOLIO PLANNING
25 25 PORTFOLIO PLANNING Deliverables associated with each Planning level Strategy to the Scrum teams DESCRIPTION Strategic Planning: month horizon, Strategy Council provides Strategic Roadmap derived from Group long term and short term strategy Portfolio Planning: 6-12 month horizon, based on the Strategic Initiative budget allocation and the priority of the Programs Program Roadmap: 2-6 month horizon, based on the Platform and Product budget allocation and the business priorities Release Planning: 2-6 month horizon, Sequencing delivery of Epics, Features, Stories based on business priority Sprint (Iteration) Planning: 1-4 sprint horizon, Delivery team commitments for Stories in the next Iteration Task Planning: One sprint horizon, Delivery team delineates stories into tasks, and assigns tasks to team members STRATEGY PORTFOLIO PROGRAM RELEASE ITERATION TASK DELIVERABLES Strategy Statement Strategic Initiative budget allocation Portfolio Roadmap Portfolio budget allocation Portfolio Priorities Program Roadmap Product budget allocation Product Priorities Epic Priorities, Epic and Feature Sequencing Delivery Team assignment Story Sequencing Delivery Team commitment Task Definition Delivery Team member commitment
26 26 PORTFOLIO MANAGEMENT BRIEF: Supports the definition and flow of epics from new concept until they are delivered or killed. PORTFOLIO PLANNING SHEET: Decisioning tool that helps determine prioritization of the release backlog. PORTFOLIO DASHBOARD: Indicator of health of epics, risks, and dependency impacts. RELEASE PLANS: Credible plan to meet release objectives. ROADMAP: Roadmap of epics into the future.
27 27 PORTFOLIO MANAGEMENT PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION STRATEGIC ALIGNMENT DEMAND MANAGEMENT DETAILED PLANNING EXECUTION GOVERNANCE MEASURE EFFECTIVENESS Maximize Strategic Alignment Increase Transparency Organizational focus on delivering the most valuable work Increase predictability Reduce Time to ROI Identify and plan for dependencies Balance capacity and demand Reduce rework Improve quality Agree to minimal capabilities needed to deliver value Ensure credible release planning Assess and guide the progress of value delivery Minimize delivery risks Continually make continue, pivot, kill, ship decisions Revisit business case Validate fitness function for capability
28 28 STRATEGIC ALIGNMENT PURPOSE Align Epics to strategy ACTIVITIES Intake all Epics, validate alignment to Strategic Objectives Ensure alignment to Business Architecture Defer Epics that are clearly not aligned to strategy OUTPUT Epic Brief initiated Strategically aligned Epics in Portfolio Backlog
29 29 BRIEF Epic Owner completes the Vision section Epic Owner and Product Owner team start the Constraints section Begin the Opportunity / Business Case DESCRIPTION VISION CONSTRAINTS Name Epic Owner/ Product Manager Investment Theme (and Capability if known) Value Statement Features/Benefits Dependencies Risks Assumptions PLANNING Opportunity Case
30 30 PORTFOLIO MANAGEMENT PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION STRATEGIC ALIGNMENT DEMAND MANAGEMENT DETAILED PLANNING EXECUTION GOVERNANCE MEASURE EFFECTIVENESS Maximize Strategic Alignment Increase Transparency Organizational focus on delivering the most valuable work Increase predictability Reduce Time to ROI Identify and plan for dependencies Balance capacity and demand Reduce rework Improve quality Agree to minimal capabilities needed to deliver value Ensure credible release planning Assess and guide the progress of value delivery Minimize delivery risks Continually make continue, pivot, kill, ship decisions Revisit business case Validate fitness function for capability
31 31 SOLUTION DEFINITION PURPOSE Validate business intent and epic viability (Aka Discovery) ACTIVITIES Validate Epic Brief Vision and Constraints Identify work to address risks and dependencies Technical Impact Assessment OUTPUT Epic Brief Vision and Constrains sections Program Backlog: Features, Architectural and Risk cards Update WSJF
32 32 BRIEF Epic Owner completes the Vision section Epic Owner and Product Owner team complete the Constraints section Prepare the brief Opportunity/Business Case DESCRIPTION VISION CONSTRAINTS Name Epic Owner/ Product Manager Investment Theme (and Capability if known) Value Statement Features/Benefits Personas Dependencies Risks Assumptions PLANNING Opportunity Case Roadmap
33 33 PORTFOLIO MANAGEMENT PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION STRATEGIC ALIGNMENT DEMAND MANAGEMENT DETAILED PLANNING EXECUTION GOVERNANCE MEASURE EFFECTIVENESS Maximize Strategic Alignment Increase Transparency Organizational focus on delivering the most valuable work Increase predictability Reduce Time to ROI Identify and plan for dependencies Balance capacity and demand Reduce rework Improve quality Agree to minimal capabilities needed to deliver value Ensure credible release planning Assess and guide the progress of value delivery Minimize delivery risks Continually make continue, pivot, kill, ship decisions Revisit business case Validate fitness function for capability
34 34 RELEASE TARGETING PURPOSE Identify and plan for dependencies Balance capacity and demand Ensure credible release planning ACTIVITIES Estimate Features Determine Capacity Plan Epics, Risks and Dependencies (Look ahead planning) Communicate release objectives and guard rails OUTPUT Epic Roadmap revised with risks and dependencies Release Plans Portfolio Plans updated Portfolio Risk Dashboard updated
35 35 BRIEF Summarize results in the Planning section of the Epic Brief as a check point to ensure sufficient planning is done DESCRIPTION VISION CONSTRAINTS Name Epic Owner/ Product Manager Investment Theme (and Capability if known) Value Statement Features/Benefits Personas Dependencies Risks Assumptions PLANNING Opportunity Case
36 36 PORTFOLIO MANAGEMENT PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION STRATEGIC ALIGNMENT DEMAND MANAGEMENT DETAILED PLANNING EXECUTION GOVERNANCE MEASURE EFFECTIVENESS Maximize Strategic Alignment Increase Transparency Organizational focus on delivering the most valuable work Increase predictability Reduce Time to ROI Identify and plan for dependencies Balance capacity and demand Reduce rework Improve quality Agree to minimal capabilities needed to deliver value Ensure credible release planning Assess and guide the progress of value delivery Minimize delivery risks Continually make continue, pivot, kill, ship decisions Revisit business case Validate fitness function for capability
37 37 IN PROGRESS PURPOSE Assess and guide the progress of value delivery ACTIVITIES Review Epic Health and Portfolio Dashboard Monitor & communicate Release Health to Stakeholders Continue, Change or Stop Decisions OUTPUT Epic Dashboard Portfolio Dashboard Portfolio Kanban Board
38 PRIORITIZATION TECHNIQUES
39 39 MOSCOW PRIORITIZATION MUST Minimum subset of requirements that must be delivered Important but not needed to have a viable solution Desired but less important WON T Things we have agreed to not deliver
40 40 COST OF DELAY If you only measure one thing, measure cost of delay - D. Reinertsen, The Principles of Product Development Flow COST OF DELAY: The revenue that could be earned each month a project is in the market
41 41 COMPARE 3 Features of a certain value with a CD3 calculation (value / duration) Total amount of value across three features is $19,000 FEATURE DURATION VALUE CD3 A 3 weeks $ B 4 weeks $ C 6 weeks $
42 42 PRIORITY IMPACT ON COST OF DELAY No Priority Total Cost of Delay: $247k Shortest Job First Total Cost of Delay: $175k Do The Most Valuable First - Total Cost of Delay: $187k DO BASED ON CD3 TOTAL COST OF DELAY: $157K
43 DEMAND MANAGEMENT
44 HOW TO EXPRESS CAPACITY? 44
45 CAPACITY CAN BE EXPRESSED AS 45 TEAM MONTHS TEAM SPRINTS TEAM RELEASES STORY POINTS Only 25% of the Team Months for Team X remain for FY17 (e.g. 3 months remaining of 12 months this year) There are 6.5 Team Sprints for Team X remaining for FY17 (e.g. 13 weeks / 2 weeks per sprint) There are 2.25 Team Releases for Team X remaining for FY17 (e.g. 13 weeks / 3 Sprints per Release) There are 150 Story Points available for the remainder of the year (e.g. Average velocity of 25 SPs x 6.5 Sprints remaining)
46 ALL WHICH DERIVE THEIR USE FROM STABLE VELOCITY! 46 TEAM MONTHS Only 25% of the Team Months for Team X remain for FY17 (e.g. 3 months remaining of 12 months this year) TEAM SPRINTS There are 6.5 Team Sprints for Team X remaining for FY17 (e.g. 13 weeks / 2 weeks per sprint) TEAM RELEASES STORY POINTS There are 2.25 Team Releases for Team X remaining for FY17 (e.g. 13 weeks / 3 Sprints per Release) There are 150 Story Points available for the remainder of the year (e.g. Average velocity of 25 SPs x 6.5 Sprints remaining) DELIVERY TEAM Meaningless without Stable Velocity.
47 CAPACITY IS INVESTED TO OBTAIN OUTCOMES MONTHS INVESTMENT THEMES % ~ 17.5 TEAM MONTHS 20% ~ 10 TEAM MONTHS 25% ~ 12.5 TEAM MONTHS 20% ~ 10 TEAM MONTHS 2O% 35% 2O% 25% Early on you can roadmap out what you re willing to invest capacity for across investment themes Program Capacity Over Next 10 Months = 50 Team Months
48 ROADMAPS
49 AGILE USES ROLLING WAVE PLANNING 49 Rolling Wave Planning, used in Agile processes, embraces the Lean ideal of making decisions at the last responsible moment, when the most possible information is available. This maximizes flexibility and planning accuracy.
50 50 ROLLING MONTHS Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 This is A Rolling Plan for months ahead A Hypothesis for how to meet the goals Not what you will do to meet those goals ROADMAP ROADMAP ROADMAP ROADMAP ROADMAP ROADMAP ROADMAP ROADMAP ROADMAP
51 51 APPLYING MOSCOW TO S Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST MUST MUST
52 52 WHAT DO WE KNOW? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T You Know A Great Deal Here
53 53 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to the could have?
54 54 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to the could have? NO
55 55 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to the wish to have?
56 56 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to the wish to have? NO
57 57 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to the could have?
58 58 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to the could have? NO
59 59 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to should and must?
60 60 WHAT DO WE COMMIT TO? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T Do you commit to should and must? YES
61 THIS IS A RELIABLE COMMITMENT 61 Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST MUST S S WON T WON T Realign to reflect the most likely outcome.
62 62 IF WE FINISH EARLY? Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T
63 63 FINISH THE ROADMAP Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST S WON T WON T
64 64 ADD NEW & REPRIORITIZE Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST MUST MUST S WON T WON T
65 65 THAT S BETTER Q Q Q Q Q Q (ACTIVE) PLANNED Q+2 Q+3 Q+4 Q+5 MUST MUST MUST S MUST MUST S MUST WON T WON T
66 DETAILED GOVERNANCE
67 67 GOVERNANCE PORTFOLIO TEAM PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION COMPLETED Epic Kanban DEFINITION (DEPENDENCIES, SIZING & RISKS) DEMAND PLANNING & RELEASE ROADMAP MEASURABLE PROGRESS PROGRAM TEAM Feature Kanban PROGRAM WORK INTAKE SOLUTION DESIGN RELEASE PLANNING FEATURE READY IN PROGRESS FEATURE VALIDATION COMPLETED DETAILED PLANNING (CLARITY & VIABILITY) EXECUTION & ACCOUNTABILITY DELIVERY TEAM Story Scrum MAKE READY STORY READY IN PROGRESS STORY DONE STORY ACCEPTED PORTFOLIO PLANNING RELEASE PLAN & DEFINE EXECUTE OPERATE
68 Portfolio Tier 68 PORTFOLIO WORK INTAKE SOLUTION DEFINITION RELEASE TARGETING IN PROGRESS VALIDATION COMPLETED PURPOSE Intake process for Initiatives to be considered Define Epics for Initiatives Validate business intent & epic viability Ensure credible release planning Identify & plan for dependencies Balance capacity & demand Assess and guide the progress of value delivery Validate solution Customer / Vendor UAT Validate Outcomes ACTIVITIES Epic Brief initiated Validate Epic & Constraints Identify work to address risks and dependencies Product Discovery and Product Validation Communicate release objectives (MVP) Sufficient release planning is captured in planning toolset Determine Capacity Plan Risks & Dependencies Review Epic Health & Portfolio Dashboard Monitor & communicate Release Health to Stakeholders Continue, Change or Stop Decisions Determine if capabilities provide expected solution Product Discovery and Product Validation User acceptance testing Work with vendors or customers for final solution validation Measure Outcomes OUTPUTS Epic Brief Draft Product Discovery and Product Validation validated with customers Epic Brief Cost Estimate Updated Business Plan Cost Case Financial Evaluation Technology Impact Assessment Portfolio Roadmap Updated Portfolio Roadmap Signoff - Initiative/Epic Portfolio Planning Sheet Release Plan Updated Risk Assessment Release Planning Signoff Initiative/Epic Epic Definition of Ready Validated Epic Dashboard Portfolio Dashboard Product Discovery and Product Validation Revalidated with customers Epic Brief updated as completed Operation Signoff Program/Epic UAT Approval Release Review Epic Definition of Done validated Execute Signoff - Epic Retrospective Analysis RACI (TEAM) R Portfolio Team Program Team A - Portfolio Team C Product Management I Delivery Team R Portfolio Team Program Team A - Portfolio Team C Product Management I Delivery Team R Portfolio Team Program Team A - Portfolio Team C Product Management I Delivery Team R Portfolio Team Program Team A - Portfolio Team C Product Management I Delivery Team R Portfolio Team Program Team A - Portfolio Team C Product Management I Delivery Team R Portfolio Team Program Team A - Portfolio Team C Product Management I Delivery Team
69 Program Tier 69 PROGRAM WORK INTAKE SOLUTION DESIGN RELEASE PLANNING FEATURE READY IN PROGRESS FEATURE VALIDATION COMPLETED PURPOSE Intake process for epics to be considered High level solution design Validate solution viability Elaborate stories from features Identify risks & dependencies Features are ready for development Credible plan exists MMF identified Assess and guide the progress of value delivery All features and stories are done for the epic Features in production ACTIVITIES Creation of initial epic for Investment Decision by the Portfolio Team Technology Assessment Identify solution options Identify work to address risks and dependencies Story mapping Estimate Features and Stories Plan Risks & Dependencies Define Test Plans Validate MMF for initiative Make release commitment Estimate Features Estimate Stories Review Epic Health & Portfolio Dashboard Monitor & communicate Release Health to Stakeholders Continue, Change or Stop Decisions Deployment to QA environments Acceptance testing by IVT Socialization of capabilities Final defect remediation NFR Validation Operational handoff Warranty support Update portfolio metrics OUTPUTS Feature Definition initiated OOM Estimates (if available) Program Backlog: Features Definition Architecture Impact Assessment Risk and Dependency Assessment Test Strategy Defined Feature Estimates UX Design High Level Design Initial Release Plan Updated risk and dependency lists Spikes identified Stories Named System Test Plan Integration Test Plan Regression Test Plan Solution Design Package Feature backlog items prioritized Feature backlog items sequenced across teams Spikes planned Release Defined UAT Plan Defined Feature Definition of Ready Validated Feature Dashboard Epic Dashboard Portfolio Dashboard Feature approval Updated documentation Traceability Matrix System Test Approval Integration Test Approval Regression tests Approval NFR Testing Approval Disaster Recovery Plan Updated Support Manual Updated Service/Operational Level Agreement Feature Definition of Done validated Features released Release criteria met No high severity defects RACI R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team R Program Team, Delivery Team A - Program Team C - Delivery Team I Portfolio Team
70 Delivery Tier 70 MAKE READY STORY READY IN PROGRESS STORY DONE STORY ACCEPTED PURPOSE Ready the backlog Stories ready for delivery teams Work is done to complete story / feature Story / feature has been completed Story / feature has been accepted ACTIVITIES Create story in defined format Create acceptance criteria in the defined format Provide additional documentation as needed Tie acceptance criteria to feature acceptance Revise Level of Value Create story tasks Develop story functionality Unit test functionality Code/Peer Review Check-in code Repair defects Story meets the definition of done Product owner approves story as meeting acceptance criteria. Bugs found for the story have been remediated Ongoing Support Operational Handoff Lessons Learned OUTPUTS User Story is Defined with Scenarios Acceptance Criteria is complete Architecture Artifacts UX Design, Wireframe Artifacts Story Point Estimate Story Definition of Ready Validated Tasks Defined Task Hours Estimate Sprint Planning Monitor Progress on Scrum Board Standup Story Development Story Unit Testing Story System Testing Story Done Story Definition of Done Validated Story Demo Story Accepted in ALM Toolset Operational documentation updated (as needed) Sprint Retrospective Delivery Team Metrics RACI R Delivery Team, Program Team A Delivery Team C Delivery Team I Program Team R Delivery Team, Program Team A Delivery Team C Delivery Team I Program Team R Delivery Team, Program Team A Delivery Team C Delivery Team I Program Team R Delivery Team, Program Team A Delivery Team C Delivery Team I Program Team R Delivery Team, Program Team A Delivery Team C Delivery Team I Program Team
71 71 WRAP UP Using portfolio management so we focus on the most valuable things Balancing capacity against demand How be adaptive and support continuous improvement How to support corporate governance (security, audit etc.)
72 72 RICK AUSTIN Information Technology Director Director of Development ABOUT ME Experience applying agile to small teams, large distributed teams, & change management Expert in Financial Services Industry Georgia State Grad Agile Transition Director, Program Manager Agile Project Management Volunteer and Leader Applications Development Manager twitter.com/rickaustin facebook.com/leadingagile linkedin.com/in/rickdaustin
Why Agile Transformations Fail. What You Need to Know to Transform Any Sized Organization into an Agile Enterprise
Why Agile Transformations Fail What You Need to Know to Transform Any Sized Organization into an Agile Enterprise DEREK HUETHER Enterprise Transformation Consultant derek@leadingagile.com 301/639-4976
More informationTHE THREE THINGS. You Need to Know to Transform Any Sized Organization into an Agile Enterprise
THE THREE THINGS You Need to Know to Transform Any Sized Organization into an Agile Enterprise MIKE COTTMEYER mike@leadingagile.com 404-312-1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile
More informationThe Integrated BA. The partnering Business Analyst / Business Architect roles. September 12, 2015 Russ Peña
The Integrated BA The partnering Business Analyst / Business Architect roles September 12, 2015 Russ Peña Enterprise Transformation Consultant @ LeadingAgile About Me Russ Peña Enterprise Transformation
More informationIBM s SAFe Solution Overview
IBM s SAFe Solution Overview Rational Team Concert V6.0 Amy Silberbauer Solution Architect, DevOps Plan & Enterprise Scaled Agile IBM Systems Application Platform & Middleware safeinfo@bg.vnet.ibm.com
More informationWe use Agile. What does that mean?
Project Methodology We use Agile. What does that mean? Traditional Project Management Agile Project Management All features and requirements are fixed at the start of the project. Project starts with a
More informationAgile Delivery Framework (ADF)
Agile Delivery Framework (ADF) Overview Agile is an iterative methodology with self-directed teams and the ability to embrace change rapidly. This document summarizes the Agile Scrum process as well as
More informationPMI Agile Certified Practitioner (PMI-ACP) Duration: 48 Hours
PMI Agile Certified Practitioner (PMI-ACP) Duration: 48 Hours Organizations that are highly agile & responsive to market dynamics complete more of their projects successfully than their slower-moving counterparts.
More informationBridging the Gap Between Governance and Agility. Mario E. Moreira
Bridging the Gap Between Governance and Agility Mario E. Moreira Approach Success Criteria Senior Management Understanding Helping define what Agile Is and Isn t Adapting Business Governance Establishing
More informationSAFe in a Nutshell SCALED AGILE FRAMEWORK
SAFe in a Nutshell SCALED AGILE FRAMEWORK CINDY LAKE INTRODUCTION Education MBA/ITM Master of Business Administration/Informational Technology Management 2010 The UNIVERSITY OF PHOENIX, Salt Lake City,
More informationIt can be done. Agile at Scale
It can be done. Agile at Scale March 31, 2017 Catalysts & Motivations for Agile Are you experiencing: Extended Delivery Timeframes from concept to launch Extensive Changes Late in the Development Cycle
More informationTHE THREE THINGS. You Must Know to Transform Any Sized Organization into an Agile Enterprise
THE THREE THINGS You Must Know to Transform Any Sized Organization into an Agile Enterprise MIKE COTTMEYER mike@leadingagile.com 404-312-1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile
More informationScaling Agile to the Enterprise
Scaling Agile to the Enterprise Enabling the Agile Enterprise Strategically Aligned, Throughput Focused, Human Powered Dennis Stevens Enterprise Agile Coach www.leadingagile.com www.dennisstevens.com OPM3:
More informationAgile at Mid-Scale. Al Shalloway. Introducing FLow for Enterprise Transformations (FLEX)
Agile at Mid-Scale Introducing FLow for Enterprise Transformations (FLEX) Al Shalloway CEO, Founder alshall@netobjectives.com @AlShalloway Co-founder of Lean-Systems Society Co-founder Lean-Kanban University
More informationCourse Title: Agile for Business Analysts
Course Title: Agile for Business Analysts 2 Day Workshop AG-BA08 Agile for Business Analysts Course ID: AG-BA08 Credits: 14 PDUs Course Duration: 2 days Course Level: Basic/Intermediate Prerequisites:
More informationARCHITECTING PROJECT MANAGEMENT for Enterprise Agility. Enable Organization with Agile using Tooling/Technology
ARCHITECTING PROJECT MANAGEMENT for Enterprise Agility July 14 to 16, 2016, NIMHANS Convention Centre, Bengaluru Enable Organization with Agile using Tooling/Technology Leverage of Technology Paper Id:
More informationCourse Title: Agile for Business Analysts
Course Title: Agile for Business Analysts 2 Day Workshop AG-BA08 Agile for Business Analysts Course ID: AG-BA08 Credits: 14: PMI-PDUs, IIBA-CDUs (Professional Development Hours) Course Duration: 2 days
More informationOrganizational Change Through Metrics
Organizational Change Through Metrics Speaker: Allen Hurst and Heather Rainey Company: Improving Enterprises Website: www.improvingenterprises.com Welcome to the PMI Houston Conference & Expo 2015 Please
More informationSAFe 4.0 Glossary. Scaled Agile Framework Terms and Definitions. English. VERSION 4.0.
SAFe 4.0 Glossary Scaled Agile Framework Terms and Definitions English TEAM PROGRAM VALUE STREAM PORTFOLIO PROVIDED BY www.scaledagileframework.com www.scaledagile.com VERSION 4.0.2 2017 Scaled Agile,
More informationAttend Learn Grow Taking Your Career to the Next Level. 4th Annual Professional Development Days! May th, 2018
Attend Learn Grow Taking Your Career to the Next Level 4th Annual Professional Development Days! May 23-24 th, 2018 Our Transition from Waterfall towards Agile Jeff Fearn Why Agile Why Today? Aggressive
More informationCriteria. Kanban. Scrum. Acceptance. Acceptance Criteria. Kanban. Scrum. Refinement. Agile Manifesto. Acceptance Test. Product Backlog.
Scrum Scrum Kanban Kanban XP XP Acceptance Criteria Acceptance Criteria Agile Manifesto Agile Manifesto Acceptance Test Acceptance Test Backlog Refinement Backlog Refinement Burndown Chart Burndown Chart
More informationThe Faster Road to Innovation Why Workopolis Went Agile
The Faster Road to Innovation Why Workopolis Went Agile What I m Covering Today Why did we transition to Agile? What we wanted to Achieve Highlights of How We Did It What we Achieved What we Learned Technology
More informationEnabling Enterprise Business Agility
Enabling Enterprise Business Agility The EBA Transformation Journey Team of Teams Agility: - Scaling Agile (SAFe) - DevOps Maturity - Leadership & Culture Talent Development, Innovation & Operational Agility:
More informationAgility at Scale. Support de la méthodologie SAFe dans la plateforme CE-ALM. Christophe Telep Offering Manager, IBM
Agility at Scale Support de la méthodologie SAFe dans la plateforme CE-ALM Christophe Telep Offering Manager, IBM Agenda IBM s point of view The recipe SAFe overview IBM s support for scaling agile Customer
More informationUnderstanding Agile from a PMP s Perspective! Exploding the myth that Agile is not in the PMBOK
Understanding Agile from a PMP s Perspective! 1 Agile experts claim their best practices are outside the PMBOK Guide but that has no basis in fact! Fact As early as PMBOK Guide 2000 Edition, it identified
More informationA Guide to Critical Success Factors in Agile Delivery
IBM Global Business Services, U.S. Federal May 6, 2016 A Guide to Critical Success Factors in Agile Delivery Paul Gorans, Agile Competency Lead, IBM GBS Federal A bit about me 6 Years USAF: NSA Operations,
More informationMaking Visions Actionable. Pejman Makhfi Certified Scrum Master VP of Solution, Savvion Inc. 11/29/2008
Making Visions Actionable Pejman Makhfi Certified Scrum Master VP of Solution, Savvion Inc. 11/29/2008 Development can t estimate and commit on what they do not fully understand Business can t freeze scope
More informationAgile Software Development Techniques for Small Scale Research Projects. how to not go down the rabbit hole
Agile Software Development Techniques for Small Scale Research Projects how to not go down the rabbit hole Henriette Koning Senior Manager Software Delivery But first... Henriette Koning (me) We will talk
More informationSEPTEMBER 2018 The Agile Team s Playbook to Doing Agile
SEPTEMBER 2018 The Agile Team s Playbook to Doing Agile A how-to guide for agile practitioners Agile is an umbrella term for a variety of work-management approaches that share common principles, among
More information/smlcodes /smlcodes /smlcodes. Small Codes. Programming Simplified. A SmlCodes.Com Small presentation. In Association with Idleposts.
/smlcodes /smlcodes /smlcodes T U T O R I A L Small Codes Programming Simplified A SmlCodes.Com Small presentation In Association with Idleposts.com For more tutorials & Articles visit SmlCodes.com 1 P
More informationScale Your Agile Delivery Engine. Shannah Van Winkle, Solutions Leader Eric Willeke, Transformation Consultant October 16, 2014
Scale Your Agile Delivery Engine Shannah Van Winkle, Solutions Leader Eric Willeke, Transformation Consultant October 16, 2014 Get Answers Now Our panel of experts is standing by to answer your questions
More informationMaureen Weverka & Kathy Burnham Mutual of Omaha. November 9, Mutual of Omaha Insurance Company. All Rights Reserved.
Maureen Weverka & Kathy Burnham Mutual of Omaha November 9, 2017 1 Company. All Rights Reserved. Fortune 500 company which strives to help their customers protect what they care about and achieve their
More informationThe Synergistic Nature of PI Objectives
The Synergistic Nature of PI Connecting the Dots Between Goals and Outcomes 1 Charlene M. Cuenca Sr Consultant and SPCT and SAFe Contributor ICON Agility Services 2 Session How PI foster consistent, ongoing
More informationBA25-Managing the Agile Product Development Life Cycle
BA25-Managing the Agile Product Development Life Cycle Credits: 28 PDUs / 4 Days Course Level: Intermediate/Advanced Course Description: This 4-day course explores how adapting Agile values and principles
More informationAgile Certified Professional
Certified Professional Study Guide Take the Certification Online www.scrumprofessionals.org Contents 1. AGILE PRIMER... 1 Roles in... 1 Cross-functional Team... 2 How an Team Plans its Work?... 3 What
More informationThe Challenge: Balancing Change and Control of Continuous Delivery at Scale
WWW.PLUTORA.COM SOLUTION BRIEF The Challenge: Balancing Change and Control of Continuous Delivery at Scale DevOps bridges the gap between development and operations to deliver business value more frequently.
More informationBuilding Cloud Apps using Agile Methodology & Tools
Building Cloud Apps using Agile Methodology & Tools Steve Greene VP, Products & Technology Program Management Salesforce.com Sue Vickers Principal Product Manager for CA Agile Vision CA Technologies Safe
More informationTSP*-Agile Blend: The Gun Smoke Clears
TSP*-Agile Blend: The Gun Smoke Clears Alan Padula TSP Symposium September 21-24, 2009 New Orleans, Louisiana 2009 Intuit Inc. All rights reserved. * SM TSP Team Software Process and TSP are service marks
More informationScrum Product Owner Course 03 - Roles and Responsibilities
Scrum Product Owner Course 03 - Roles and Responsibilities Course Slide 1 Roles and Responsibilities Topics Covered Product Owner Role Scrum Master Role Scrum Team Role Other Roles Slide 2 Learning Objectives
More informationIntroduction 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
More informationScrum Team Roles and Functions
Scrum Team Roles and Functions What is a Scrum Team? The purpose of a Scrum team is to deliver products iteratively and incrementally, maximizing opportunities for feedback Scrum teams are comprised by
More informationRussell Pannone February 10, 2009
Russell Pannone February 10, 2009 webeagile@aol.com About Me 27 years of System/Software Product Development Experience Developer Data Modeler Team Lead Project Manager Certified Scrum Master/Certified
More informationAgile Mindset (1/17/2019 for the Ocean State PMI)
Get connected with Leapfrog LeapFrog Systems Agile Mindset (1/17/2019 for the Ocean State PMI) Agenda 1. What is Agile? 2. Compare Agile and Traditional SDLC s 3. Agile Delivery Frameworks Scrum, Kanban,
More informationApplying Lean-Agile practices Large, Engineered Systems. Harry Koehnemann. SAFe Consultant and Fellow Scaled Agile, Inc.
Applying Lean-Agile practices Large, Engineered Systems Harry Koehnemann SAFe Consultant and Fellow harry@scaledagile.com 1 Agenda Overview of Lean-Agile principles Apply Lean-Agile principles to engineered
More informationProduct Council Approval EOY Review Q2. Produ ct Counc il: Appro val. PM + UX: Likely Case. Y e s. il: Conce pt N. Sprint Planning
WELCOME! Process Overview Process End-to-End Client, Research, Market, Sales, Support R Responsible W h o t a s k? A Accountable W i s d o i n g t h e h o m a k e s t h e d e c i s i o n a n d h a s u
More informationA practical guide to governance of enterprise-scale Agile projects. 4 October 2011
A practical guide to governance of enterprise-scale Agile projects 4 October 2011 What are we talking about! Governance of enterprise-scale Agile projects What is Governance? What is enterprise-scale Agile?
More informationAGILE Realities. Presenters: Chris Koo (Edward Jones) Blake Moyer (Edward Jones) Joan Romine (Boeing)
AGILE Realities Presenters: Chris Koo (Edward Jones) Blake Moyer (Edward Jones) Joan Romine (Boeing) 1 AGILE Gaining Momentum 2 AGILE First Impressions Fast! Flexible! 3 AGILE Development Myths "Agile
More informationJohanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right. Copyright 2017
Johanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right Copyright 2017 Start you Agile project right Projects need direction teams need to know where
More informationDriving Business Agility the Product Way
Driving Business Agility the Product Way The New World of Business Agility Asymmetric competition is disrupting industries at an unprecedented rate. Born digitals like Amazon and Alibaba continually deliver
More informationDESJARDINS NEXT DELIVERY APPROACH. New Enterprise in Expansion and Transformation (NeXT) Case Study February 22, 2018
DESJARDINS NEXT DELIVERY APPROACH New Enterprise in Expansion and Transformation (NeXT) Case Study February 22, 2018 IMPORTANT THINGS TO KNOW This case study is presented by Levio, a DAC Bronze Partner,
More informationCopyright Intertech, Inc All Rights Reserved. May 18, 2011
Copyright Intertech, Inc. 2011. All Rights Reserved. May 18, 2011 About Me Dave Schueck Principal Consultant Intertech Dschueck@Intertech.com 20 years experience Variety of technologies, roles, systems,
More informationBusinesses now operate in rapidly changing environment.
Computers II Lesson 3 3.0 Agile software development Businesses now operate in rapidly changing environment. They have to respond to new opportunities and markets, changing economic conditions, and the
More information7 Misconceptions of Enterprise Agile. August 15
7 Misconceptions of Enterprise Agile August 15 Misconception #1 Enterprise Agile will free you from having to do requirements 5/1/13 Copyright 2013 Blueprint 2013 Software Blueprint Systems Inc. All Rights
More informationITBraindumps. Latest IT Braindumps study guide
ITBraindumps http://www.itbraindumps.com Latest IT Braindumps study guide Exam : PK0-004 Title : CompTIA Project+ Exam Vendor : CompTIA Version : DEMO Get Latest & Valid PK0-004 Exam's Question and Answers
More informationEmbracing SAFe. The Process and Tooling for Enterprise Scaled Agile in IBM s Continuous Engineering Solution
Embracing SAFe The Process and Tooling for Enterprise Scaled Agile in IBM s Continuous Engineering Solution Amy Silberbauer Solution Architect, Enterprise Scaled Agile Watson IoT Connected Products Offering
More informationAuthor : Pranay K Chanda, Cognizant Agile Practice
Author : ranay K Chanda, Cognizant Agile ractice Agenda 1 Traditional ortfolio Management 2 Lean-Agile Budgeting Operating Model 3 Lean-Agile Budgeting Best ractices 4 Q & A 2 Traditional ortfolio Management
More informationAGILE INTERNAL AUDIT (IA)
AGILE INTERNAL AUDIT (IA) JENNIFER M. SCHWIERZKE MANAGING DIRECTOR UNITED AIRLINES Jennifer is a managing director in the Internal Audit department at United Airlines. She has responsibility for Finance,
More informationVisit California Digital Solutions, Drupal Development Website Experience. ITRS Case Study.
Visit California Digital Solutions, Drupal Development Website Experience ITRS Case Study www.appnovation.com ITRS CASE STUDY Contents 1.0 Project Overview P.3 P.4 2.1 Primary Project Solutions, Completed
More informationUse Cases and User Stories for Agile Requirements
Use Cases and User Stories for Agile Peter Schmidt, PMP, PMI-ACP, CPL VP, Client Services, ESI International pschmidt@esi-intl.com www.esi-intl.com Agenda 1 2 3 Principles Identify the principles that
More informationThe Power of Visibility: Driving a Lean-Agile Transition. Kelley Horton Director, Corporate IT Program Management Office
The Power of Visibility: Driving a Lean-Agile Transition Kelley Horton Director, Corporate IT Program Management Office The Power of Visibility - Agenda About Premier, Inc. Why we transitioned to Lean-Agile
More informationHarnessing the Power of Agile. Krishna Srinivasan Boris Cononetz, Jr.
Harnessing the Power of Agile Krishna Srinivasan Boris Cononetz, Jr. Harnessing the power of agile development Leverage agile development to integrate complex business environments to your PLM platform
More informationScale. Becoming a Lean Enterprise with IBM and SAFe
Agile @ Scale Becoming a Lean Enterprise with IBM and SAFe Amy Silberbauer Solution Architect, Enterprise Scaled Agile Watson IoT ALM Offering Management Team asilber@us.ibm.com 1 Watson / Presentation
More informationTitle : Analytics in Agile Project Management Theme: Project Management Leadership > In a Rapidly Changing World Keywords: Agile, Metrics, Analytics, Regression Model Abstract: In the Information revolution
More informationAuthor: Rahul Sudame Title of the Paper: My 12 Agile blunders! Theme: Project Management Leadership > In a Rapidly Changing World Keywords: Agile, Scrum, Scaling, Lessons Learned Abstract: Many Agile enthusiast
More informationAGILE TOOLS BEST PRACTICES AND LESSONS LEARNED. Presenter: Travis K. Anderson, PMP, SAFe Agilist Date: September 25 th, 2018
AGILE TOOLS BEST PRACTICES AND LESSONS LEARNED Presenter: Travis K. Anderson, PMP, SAFe Agilist Date: September 25 th, 2018 ABSTRACT In today s hyper dynamic world of projects, resilience and agility are
More informationBusiness Analyst and Product Owner Where do they meet & conflict? Cherifa Mansoura
Business Analyst and Product Owner Where do they meet & conflict? Cherifa Mansoura www.linkedin.com/in/linkedincherifamansoura Introduction BA responsibilities in an agile environment PO Responsibilities
More informationapproach to successful project
1 The NYS Forum, Inc. Using an Agile / Waterfall Hybrid approach to successful project delivery Presented by Matthew Carmichael Project Management Workgroup 2 When to use Waterfall Projects that require
More informationIBM Collaborative Lifecycle Management & SAFe
IBM Collaborative Lifecycle Management & SAFe IBM s support for the Scaled Agile Framework V3.0 methodology in the IBM CLM solution Ibm.biz/safesupport Presented by: Amy Silberbauer Solution Architect,
More informationBraindumpsVCE. Best vce braindumps-exam vce pdf free download
BraindumpsVCE http://www.braindumpsvce.com Best vce braindumps-exam vce pdf free download Exam : PK0-004 Title : CompTIA Project+ Exam Vendor : CompTIA Version : DEMO Get Latest & Valid PK0-004 Exam's
More informationAgile Certified Practitioner (ACP) Exam Prep Course 7 Adaptive Planning
Agile Certified Practitioner (ACP) Exam Prep Course 7 Slide 1 Slide 2 Domain Tasks Levels of Planning 1. Plan at multiple levels (strategic, release, iteration, daily) creating appropriate detail by using
More informationBecoming More Agile: How to Adopt Agile Development Methodology
Becoming More Agile: How to Adopt Agile Development Methodology Becoming More Agile: How to Adopt Agile Development Methodology Salient CRGT has a 25-year history of delivering innovative, missioncritical
More informationQuality Management_100_Quality Checklist Procedure
Quality Management_100_Quality Checklist Procedure Last updated 05/15/2017 Audience: Project Team, Process Owners, Project Management Office Frequency: As Required This procedure provides detailed information
More informationVALUE FOCUSED DELIVERY
VALUE FOCUSED DELIVERY 2018 417 N 2nd Ave. Minneapolis, MN 55401 Table of Contents Project Methodology... 3 Figure 1: - Project Approach... 4 Phase 1 The Inception Sprint... 5 Figure 2: Discovery Phase
More informationCreating an Agile PMO via Scrum
Creating an Agile PMO via Scrum Deliver PMO Value Early and Often Utilize Scrum to be Operationally Effective and Efficient Paul Thomas Gilchrest; CSM, ITIL v3, PMP COO & Principal PMO Managing Director
More informationCNS Digital Transformation - Merging Two Legacy ERPs Into Single ERP Solution On SAP HANA
CNS Digital Transformation - Merging Two Legacy ERPs Into Single ERP Solution On SAP HANA v Michael P. Muir Michael.Muir@cns.doe.gov Director, Business Applications UNCLASSIFIED This document has been
More informationProduct Management Best Practices
Product Management Best Practices VP Product, Payload Technologies Rosalee Gordon Founder and VP, Product Calgary Association Executive Director, Calgary Associate Product Manager (APM) Program Deal screener,
More informationChild Welfare Services New System Project. Requirements Management Plan
Child Welfare Services New System Project Requirements Management Plan September 2017 Revision History REVISION HISTORY REVISION/VERSION # DATE OF RELEASE AUTHOR SUMMARY OF CHANGES Version 1.0 October
More informationWhy We Need More Than MVPs
w h i t e p a p e r Why We Need More Than MVPs by Al Shalloway INTRODUCTION A critical aspect of the focus on achieving business agility includes identifying what is of value to build and then manifesting
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 18 Scrum: High-Level Planning 1 Multilevel Planning in Scrum Scrum defines only sprint planning and daily planning (via the daily scrum). However,
More informationAgile Software Development in a Regulated Environment. Natalie Custer
Agile Software Development in a Regulated Environment Natalie Custer Disclaimer This presentation represents the understanding of the presenter on the topic addressed. It does not in anyway, form or like
More informationApply an Agile Approach to Your Marketing
Apply an Agile Approach to Your Marketing Jim Ewel @jimewel Agenda Brief Overview of Agile Marketing User Stories @jimewel What is Agile Marketing? Agile Marketing is an approach to marketing that takes
More informationIntroduction... 1 Part I: Understanding Agile... 7
Contents at a Glance Introduction... 1 Part I: Understanding Agile... 7 Chapter 1: Modernizing Project Management...9 Chapter 2: The Agile Manifesto and Principles...19 Chapter 3: Why Agile Works Better...43
More informationDEVOPS. Know about DevOps.
DEVOPS Know about DevOps www.hcltech.com Practice Snapshot FOCUS AREAS (PEOPLE, PROCESS AND TOOLS) Continuous Planning Continuous Integration Continuous Quality & compliance Env Config & Release Mgmt Feedback
More informationTransformation Strategy Session
Transformation Strategy Session Agenda Drivers for Change Business Agility Overview* Baseline Health Assessment Transformation Vision and Success Measures Transformation Scope, Backlog and Roadmap Transformation
More informationOur Software Delivery Methodology What to Expect in the Development Process
What to Expect in the Development Process This overview of our Agile development process contains information that you need to know before we start your software project. It explains your role and responsibilities
More informationAGILE GOVERNANCE TRICK OR TREAT?
AGILE GOVERNANCE TRICK OR TREAT? 30 th October 2018 Matthew Taylor, IndigoBlue IndigoBlue Part of the Mastek Group TONIGHT S MENU Agile governance in three parts Concepts Initiation Delivery What is Agile?
More informationAligning Technical Requirements with Agile Development
Earned Value Management Practitioners Forum 2018 Aligning Technical Requirements with Agile Development Matthew Strain (CACI) 1 Learning Objectives Change Controlled Defining Plans Process Investigation
More informationA Journey & How it Works for Clients
A Journey & How it Works for Clients My QUICK Journey We had issues with Responding to a rapidly shifting market? How to get functionality to sales & clients faster How to better deliver
More informationSalesforce Governance: A New Hope
The purpose of governance is to provide a framework of policies, procedures & standards to ensure effective execution of projects / programs and provide strategic decision support & alignment bridging
More informationUNLEASH THE NEW: STATE GOVERNMENTS GET AGILE
UNLEASH THE NEW: STATE GOVERNMENTS GET AGILE Agile at Scale Implementing the Discipline in State Government Host Eric Sweden Program Director Enterprise Architecture & Governance NASCIO 1 States Participating
More informationChallenges of Agile Development with an External Vendor: A Case Study. Bhushan Gupta Nike Inc.
Challenges of Agile Development with an External Vendor: A Case Study Bhushan Gupta Nike Inc. October 16, 2013 Agenda Background Challenges and Potential Solutions Conclusions Q&A Background Vendor Customer
More informationAgile Testing Without Automation
Agile Testing Without Automation John Duarte, Eric Thompson john.duarte@puppet.com, erict@puppet.com Abstract Most research on Agile Testing and QA have requirements on highly automated testing and an
More informationVendor: GAQM. Exam Code: CSM-001. Exam Name: Certified Scrum Master (CSM) Version: Demo
Vendor: GAQM Exam Code: CSM-001 Exam Name: Certified Scrum Master (CSM) Version: Demo QUESTION 1 What is the maximum amount of time that the team should spend in the daily scrum? A. As long as it takes
More informationCS314 Software Engineering Project Management
CS314 Software Engineering Project Management Dave Matthews Software process movements Predictive 1970 Waterfall Iterative 1980s, 1990s Spiral, RAD, RUP Adaptive (Agile) late 1990s XP, Scrum, Crystal,
More informationScrum Intro What s in it for me?
Scrum Intro What s in it for me? Prepared by Bachan Anand Please dial in to (218) 895-4640 PIN: 3289145 Agenda Overview of Agile and Scrum Scrum: Vision and Product Scrum: Sprint What s in it for me Please
More informationAGILE LESSONS FROM THE NEW PMBOK. Presented by Eddie Merla, PMI-ACP, PMP
AGILE LESSONS FROM THE NEW PMBOK Presented by Eddie Merla, PMI-ACP, PMP 2 Agenda Summary of Changes Agile Concepts Five Mindset Shifts Agile Methods & Scrum Q&A Wrap-up 3 Summary of Changes Project managers
More information7 Agile Best Practices for BA s
7 Agile Best Practices for BA s Jiri Walek VP Product Management Clara Vincenc Cismaru Product Manager Agenda 01 How BA fits into Agile 02 7 Agile Best Practices 03 Conclusion 04 Questions & Answers +
More informationTwo Branches of Software Engineering
ENTERPRISE SOFTWARE ENGINEERING & SOFTWARE ENGINEERING IN THE ENTERPRISE Two Branches of Software Engineering 1 Crafting Software Resource Input Code Debug Product Test 2 Engineering Software Resource
More information"Charting the Course to Your Success!" Planning and Managing Agile Projects Course Summary
Course Summary Description This 3-day course aims at introducing its attendees to the core values, principles, and practices of Agile. This course is a more elaborate version of the Certified Scrum Master
More informationAgile Risk Management
Identify Assess Execute Plan Response Agile Risk Management Presented by: Susan Parente PMP, PMI-RMP, PMI-ACP, CSM, CSPO, PSM I, CISSP, CRISC, RESILIA, ITIL, MS Eng. Mgmt. Associate Professor, Post University,
More informationAgile Scrum Process Checklist
Agile Scrum Process Checklist To be successful, agile projects require a consistent management process. This checklist provides the various roles involved in agile projects (especially those with limited
More information