September 20, 2017 Agile Techniques Workshop Susan Futey

Slides:



Advertisements
Similar presentations
Project Name Kelly Waters July Author: Date: Version:
Advertisements

Chapter 5 – Enterprise Analysis
Iteration Planning.
The Business Analyst Role in Agile Projects
Agile Software Engineering Frank Maurer Agile Software Engineering Lab, University of Calgary
COMP 350: Object Oriented Analysis and Design Lecture 2
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Managing a Project Using an Agile Approach and the PMBOK® Guide
Kris Hicks-Green April 23, 2013 IIBA Austin
CHAPTER 19 Building Software.
An Agile View of Process
Sections2.4: Plan Business Analysis Communication 2.5 Plan Requirements Management Process 2.6 Manage Business Analysis Performance Kristee Watts May 7,
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
What is Business Analysis Planning & Monitoring?
QAD's Customer Engagement Dan Blake Consultancy Development Director, QAD QAD Explore 2012.
RUP Requirements RUP Artifacts and Deliverables
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
Develop Project Charter
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Software Engineering (CSI 321) An Agile View of Process 1.
January 24, 2009 Agile Product Management Making Things Happen Walter Bodwell Planigle.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
CSE Senior Design II Staged Delivery Instructor: Manfred Huber Partially adapted from Mike O’Dell.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Strategy Mapping Clear path to a successful Agile strategy Dave Neuman Sep 24, 2015 LinkedIn:
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Process 4 Hours.
The Strategic Role of Information Development in Continuous Delivery
Agile Project Management Methodology Scrum Overview
Scrum.
Scope Planning.
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Fundamentals of Information Systems, Sixth Edition
Information Technology Project Management – Fifth Edition
By: By: Agile Scrum Master Online Training.
Requirements and User Stories
Product Backlog List of things that needs to be done to make the product come into existence 
Process Improvement With Roles and Responsibilities explained
Chapter 3: The Project Management Process Groups: A Case Study
Software Engineering (CSI 321)
Rapid software development
Using Kanban Techniques to Control Incremental Development
Requirements and the Software Lifecycle
COMP 350: Object Oriented Analysis and Design Lecture 2
Project Management and the Agile Manifesto
Day 1 Big Room Planning 8:00 - 9:00
How to Successfully Implement an Agile Project
Critical Changes to PMBOK6
Summarizing Our Models to Date
Guidance notes for Project Manager
Atern v2 – Summary of changes from v1
Project Ideation Agile Down-to-Earth © 2016.
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Introduction to Agile Blue Ocean Workshops.
Twin Cities Business Architecture Forum 1/19/2016
Employee engagement Delivery guide
Scrum in Action.
Iteration Planning.
INTERACTION DESIGN IN PRACTICE
AgilityHealth® ScrumMaster Training
Presentation transcript:

September 20, 2017 Agile Techniques Workshop Susan Futey IIBA Denver Chapter September 20, 2017 Agile Techniques Workshop Susan Futey

Tonight’s Format Agile Extension V2 Classroom-style Presentation and Overview Agile Techniques Overview Vote for Agile Techniques that interest you Pick up 3 sticky notes Choose 3 techniques you wish to learn more about Cast your vote by placing sticky note on chosen technique(s) Break-out Sessions Review Technique 1, Discuss and Prepare, Present to Group Review Technique 2, Discuss and Prepare, Present to Group IIBA Denver Chapter : Agile Techniques Workshop

Agile Extension v2

How to View Agile Extension Version 2 IIBA Denver Chapter : Agile Techniques Workshop

How to View Agile Extension Version 2 IIBA Denver Chapter : Agile Techniques Workshop

The Gist Agile Mindset Horizons Techniques Agile is a mindset, not a methodology, that can be applied to business analysis competencies and techniques Horizons Business Analysis at multiple planning horizons Strategy Horizon Initiative Horizon Delivery Horizon Techniques Selecting the right technique as an agile business analysis practitioner IIBA Denver Chapter : Agile Techniques Workshop

The Agile Mindset IIBA Denver Chapter : Agile Techniques Workshop

Three Horizons IIBA Denver Chapter : Agile Techniques Workshop

Techniques Relative Estimation Backlog Refinement Retrospectives Behaviour Driven Development Impact Mapping Job Stories Kano Analysis Minimal Viable Product Personas Planning Workshops Portfolio Kanban Product Roadmap Purpose Alignment Model Real Options Relative Estimation Retrospectives Reviews Spikes Storyboarding Story Decomposition Story Elaboration Story Mapping User Stories Value Modelling Value Stream Mapping Visioning IIBA Denver Chapter : Agile Techniques Workshop

Selecting the Right Technique Communication . . . Planning Workshop, Retrospectives Process Analysis . . . Impact Mapping Product Management or Refinement Product Roadmap, Kano Analysis, Minimal Viable Product Requirements Management Spikes, Story Mapping, User Stories Understanding Your Customer Personas, Storyboarding IIBA Denver Chapter : Agile Techniques Workshop

Let’s Vote!

Tonight’s Format Agile Extension V2 Classroom-style Presentation and Overview Agile Techniques Overview Vote for Agile Techniques that interest you Pick up 3 sticky notes Choose 3 techniques you wish to learn more about Cast your vote by placing sticky note on chosen technique(s) Break-out Sessions Review Technique 1, Discuss and Prepare, Present to Group Review Technique 2, Discuss and Prepare, Present to Group IIBA Denver Chapter : Agile Techniques Workshop

Techniques Relative Estimation Backlog Refinement Retrospectives Behaviour Driven Development Impact Mapping Job Stories Kano Analysis Minimal Viable Product Personas Planning Workshops Portfolio Kanban Product Roadmap Purpose Alignment Model Real Options Relative Estimation Retrospectives Reviews Spikes Storyboarding Story Decomposition Story Elaboration Story Mapping User Stories Value Modelling Value Stream Mapping Visioning IIBA Denver Chapter : Agile Techniques Workshop

Break-out Sessions

Tonight’s Format Agile Extension V2 Classroom-style Presentation and Overview Agile Techniques Overview Vote for Agile Techniques that interest you Pick up 3 sticky notes Choose 3 techniques you wish to learn more about Cast your vote by placing sticky note on chosen technique(s) Break-out Sessions Review Technique 1, Discuss and Prepare, Present to Group Review Technique 2, Discuss and Prepare, Present to Group IIBA Denver Chapter : Agile Techniques Workshop

Appendix

Context: Product Management Refinement 7.6 Minimal Viable Product (MVP) Identifies the smallest set of features or requirements to deliver value in shortest time possible Focuses on core features and no more Further features developed after feedback IIBA Denver Chapter : Agile Techniques Workshop

Context: Product Management Refinement 7.10 Product Roadmap Strategic document and plan describing how a product will grow to align to stakeholders’ needs Shows features and a path to deliver them over time Focuses on product/feature delivered, not milestones or check points IIBA Denver Chapter : Agile Techniques Workshop

Context: Product Management Refinement 7.11 Purpose Alignment Model A two-dimensional rating model Aids in making prioritization decisions IIBA Denver Chapter : Agile Techniques Workshop

Context: Product Management Refinement 7.12 Real Options Indicates when a decision should be made and when more details are needed Frequently used as a refinement and prioritization technique Helps stakeholders delay decisions to the last responsible moment and focus on highest priority item IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.2 Behaviour Driven Development (BDD) Uses customer readable, domain specific language to specify intended behaviour Creates opportunity for test automation Examples expressed in Gherkin Syntax: IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.4 Job Stories Represent a product backlog item (PBI) or requirement in terms of a job to be done by a stakeholder Facilitate collaboration and focus the delivery team on the customer need rather than implementation details Example format: IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.13 Relative Estimation Make future predictions based on past experience Measured as story points based on what the team knows about the story: IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.16 Spikes Used to time-box research, design, or prototyping activities in order to understand expected effort Exploratory only; do not produce a potentially shippable product Often are technical, may prototype a solution approach to a feature IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.18 Story Decomposition Define requirements at progressively smaller levels of granularity IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.19 Story Elaboration Define the detailed design and acceptance criteria to deliver a working solution Lowest level of Story Decomposition and done on a just-in-time basis for stories in scope for upcoming iteration Outcome is a shared understanding of what will be delivered to achieve “Done” for this story IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.20 Story Mapping Provides view of sequence of activities to be supported by a solution Assists with prioritizing product delivery IIBA Denver Chapter : Agile Techniques Workshop

Context: Requirements Management 7.21 User Stories Representation of the customer need expressed as a concise statement of a feature Card, Conversation, Confirmation Example format: IIBA Denver Chapter : Agile Techniques Workshop