This document provides an overview of numerous agile concepts, frameworks, and practices. It includes concepts related to lean, scrum, kanban, design thinking, and scaled agile frameworks. The document also discusses challenges organizations may face in implementing agile and how an agile delivery partner can help address common issues through various agile services.
LAST Conference 2016 Agile Landscape Presentation v1Chris Webb
油
The document provides an overview of numerous agile frameworks and practices mapped on a single "Agile Landscape" diagram to help structure conversations with clients and demystify the agile umbrella. It includes a brief description of the purpose of the Agile Landscape and notes that it covers over 150 frameworks and practices ranging from well-known ones like Scrum, Kanban, and SAFe to more specialized approaches.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
The document provides an introduction to agile methods for executives. It discusses how agile approaches can help organizations adapt to increasingly volatile business environments. The key benefits of agile include shorter time to market, increased productivity, improved alignment with business needs, and greater predictability. The document outlines agile concepts like iterative development, minimal viable products, continuous delivery and focus on customer value. It also summarizes common agile frameworks like Scrum and how agility can be scaled in large organizations.
This document provides an overview of Agile project management principles and practices. It begins with introductions of the presenter and their experience in Agile software development. It then discusses various project methodologies like Waterfall, Kanban, Scrum, and Test Driven Development. Key Agile principles are outlined from the Agile Manifesto. The roles of Product Owner, Scrum Master, and development team are defined. Practices like sprint planning, daily standups, reviews and retrospectives are described. The document aims to provide a high-level introduction to Agile concepts, roles and processes.
This Hands-on Agile webinar addresses the agile maturity and a possible agility assessment of organizations before the start of an agile transition.
Moreover, learn about the survey results what indicates an agile organization, whether agile maturity is a fad, and what the open source project of the Agility Assessment Framework is about.
BLOG: https://age-of-product.com/webinar-agile-maturity/
YOUTUBE: Tba.
The document discusses goals for adopting agile practices like predictability, quality, early ROI, lower costs, and innovation. It then covers considerations for transformation based on organization size, dependencies between teams, and resistance to change. Finally, it outlines key elements of transformation including backlogs, teams, and working tested software and discusses governance structures with portfolio, program, and delivery teams.
The scrum process document outlines the key aspects of running a scrum project. It includes preparation steps like establishing a business case and assembling a team. It then describes the sprint planning meeting where the product backlog is reviewed and the sprint backlog is created. Each sprint involves daily stand up meetings and culminates in a sprint review and retrospective. The goal is to deliver working software increments in short iterations through an adaptive, flexible process.
An Introduction to Scaled Agile Framework (SAFe)CA Technologies
油
To compete in todays application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe速), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe速). Find the truth behind the often cited sentence As Scrum is to the Agile team, SAFe速 is to the Agile enterprise.
This document contains a list of over 200 terms related to agile software development methods and practices. No additional context or explanations are provided for the terms.
Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
Basic agile and lean methods
Scrum of Scrums
SAFe
Disciplined Agile Delivery (DAD)
Agility at Scale (Ambler/Lines)
Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
The document discusses challenges with enterprise agile transformations and proposes solutions. It notes that while having agile teams is good, true enterprise agility requires alignment across the organization. Focusing only on teams can cause problems if other areas are not adapted. True agile practices require changes at all levels from teams to portfolio. The solution involves establishing the right competencies at each level, adapting practices for scale and cadence, and addressing organizational structure, processes, and culture changes together.
This document provides an overview of Agile and Scrum methodologies. It describes the iterative incremental model and compares it to the waterfall model. The key aspects of Agile include iterative development, early delivery of working software, collaboration between business and developers, self-organizing teams, and face-to-face communication. Scrum is then introduced as a framework for implementing Agile. The core Scrum roles, events, artifacts, user stories, estimation techniques, and burn down charts are defined and explained at a high level.
The document provides an overview of Agile methodology and Scrum framework. It describes that Agile is an alternative project management approach that uses short iterative cycles called sprints to incrementally deliver working software. Scrum is the most commonly used Agile framework and involves roles of Product Owner, Scrum Master, and team. It uses artifacts like Product Backlog and Sprint Backlog and events like Sprint Planning, Daily Scrum, and Sprint Review.
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
Agile Transformation is a consulting firm that specializes in organizational transformation using Agile, Lean, and other methods. They help clients transform their processes, teams, and culture to improve performance. Their services include assessing needs, developing custom roadmaps, coaching teams in Agile practices, and training leaders in skills like servant leadership and collaboration. Clients praise how Agile Transformation helped them successfully transform their culture, empower teams, and bridge gaps between departments.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
This slide deck shares my thoughts on the product owner role. It discusses what it means to own a product, and how the product owner role can be scaled.
This document provides an introduction to Agile Scrum methodology. It defines Agile and Scrum, outlines the history and principles of Scrum, and describes the core components and processes in Scrum including roles, ceremonies, artifacts, and sprints. The document explains that Scrum is an iterative Agile framework used for managing complex projects, with self-organizing cross-functional teams working in short sprints to deliver working software increments based on prioritized backlogs.
This document provides an overview of agile methodology for software development. It discusses how agile practices arose in response to the limitations of traditional waterfall approaches. The core principles of agile include valuing individuals and interactions, working software, customer collaboration, and responding to change. Agile methods embrace changing requirements, frequent delivery of working software, collaboration between business and technical teams, self-organizing teams, and continuous improvement.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
Overview on Agile, Scrum, Kanban, Extreme programming (XP) and Scaled Agile F...Hyder Baksh
油
Unlock the power of Agile methodologies with this concise overview. Delve into the core principles and practices of Agile, Scrum, Kanban, Extreme Programming (XP), and the Scaled Agile Framework (SAFe) in just a few slides.
Discover how Agile methodologies revolutionize project management, emphasizing adaptability, collaboration, and customer-centricity. Learn about Scrum's structured framework, Kanban's visualized workflow, XP's engineering practices, and SAFe's scalable enterprise implementation.
Explore the benefits and challenges each methodology brings, and gain insights into selecting the right approach for your projects. Real-world case studies offer a glimpse into successful Agile transformations. Join us to uncover the essentials of Agile methodologies in today's fast-paced business landscape
The document provides an overview of an Agile Basics presentation. It includes an agenda that covers why Agile is used, popular Agile implementations like Scrum and Extreme Programming, and the landscape of Agile adoption. It also discusses benefits of Agile like releasing working software frequently and collaborating with customers, as well as common Agile practices.
For those new to Agile there is often an assumption made that the Scrum Master and the Project Manager are the same role.This is absolutely not the case. The two roles are very different and they each fit into approaches to projects that are wildly different as Agile is a Value and Culture driven Project Management Methodology.
I try to address some of the misunderstandings of the Scrum Master Role
You can see some of Scrum Master internal training videos that I did in past.
https://www.youtube.com/my_videos?o=U
How to Become an Indispensable Scrum Master
Kanban 101 workshop by John Goodsen and Michael Sahota. This is used to introduce Kanban and situate the workshop.
Please ask us if you would like PPT version.
Scrum is a framework for project management developed by Ken Schwaber and Jeff Sutherland. It is lightweight, simple, and difficult to master. Scrum uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like product backlogs and sprint backlogs. The goals are transparency, inspection, and adaptation. Scrum aims to deliver working software frequently through short development cycles and continuous improvement.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe速), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe速). Find the truth behind the often cited sentence As Scrum is to the Agile team, SAFe速 is to the Agile enterprise.
This document contains a list of over 200 terms related to agile software development methods and practices. No additional context or explanations are provided for the terms.
Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
Basic agile and lean methods
Scrum of Scrums
SAFe
Disciplined Agile Delivery (DAD)
Agility at Scale (Ambler/Lines)
Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
The document discusses challenges with enterprise agile transformations and proposes solutions. It notes that while having agile teams is good, true enterprise agility requires alignment across the organization. Focusing only on teams can cause problems if other areas are not adapted. True agile practices require changes at all levels from teams to portfolio. The solution involves establishing the right competencies at each level, adapting practices for scale and cadence, and addressing organizational structure, processes, and culture changes together.
This document provides an overview of Agile and Scrum methodologies. It describes the iterative incremental model and compares it to the waterfall model. The key aspects of Agile include iterative development, early delivery of working software, collaboration between business and developers, self-organizing teams, and face-to-face communication. Scrum is then introduced as a framework for implementing Agile. The core Scrum roles, events, artifacts, user stories, estimation techniques, and burn down charts are defined and explained at a high level.
The document provides an overview of Agile methodology and Scrum framework. It describes that Agile is an alternative project management approach that uses short iterative cycles called sprints to incrementally deliver working software. Scrum is the most commonly used Agile framework and involves roles of Product Owner, Scrum Master, and team. It uses artifacts like Product Backlog and Sprint Backlog and events like Sprint Planning, Daily Scrum, and Sprint Review.
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
Agile Transformation is a consulting firm that specializes in organizational transformation using Agile, Lean, and other methods. They help clients transform their processes, teams, and culture to improve performance. Their services include assessing needs, developing custom roadmaps, coaching teams in Agile practices, and training leaders in skills like servant leadership and collaboration. Clients praise how Agile Transformation helped them successfully transform their culture, empower teams, and bridge gaps between departments.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
This slide deck shares my thoughts on the product owner role. It discusses what it means to own a product, and how the product owner role can be scaled.
This document provides an introduction to Agile Scrum methodology. It defines Agile and Scrum, outlines the history and principles of Scrum, and describes the core components and processes in Scrum including roles, ceremonies, artifacts, and sprints. The document explains that Scrum is an iterative Agile framework used for managing complex projects, with self-organizing cross-functional teams working in short sprints to deliver working software increments based on prioritized backlogs.
This document provides an overview of agile methodology for software development. It discusses how agile practices arose in response to the limitations of traditional waterfall approaches. The core principles of agile include valuing individuals and interactions, working software, customer collaboration, and responding to change. Agile methods embrace changing requirements, frequent delivery of working software, collaboration between business and technical teams, self-organizing teams, and continuous improvement.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
Overview on Agile, Scrum, Kanban, Extreme programming (XP) and Scaled Agile F...Hyder Baksh
油
Unlock the power of Agile methodologies with this concise overview. Delve into the core principles and practices of Agile, Scrum, Kanban, Extreme Programming (XP), and the Scaled Agile Framework (SAFe) in just a few slides.
Discover how Agile methodologies revolutionize project management, emphasizing adaptability, collaboration, and customer-centricity. Learn about Scrum's structured framework, Kanban's visualized workflow, XP's engineering practices, and SAFe's scalable enterprise implementation.
Explore the benefits and challenges each methodology brings, and gain insights into selecting the right approach for your projects. Real-world case studies offer a glimpse into successful Agile transformations. Join us to uncover the essentials of Agile methodologies in today's fast-paced business landscape
The document provides an overview of an Agile Basics presentation. It includes an agenda that covers why Agile is used, popular Agile implementations like Scrum and Extreme Programming, and the landscape of Agile adoption. It also discusses benefits of Agile like releasing working software frequently and collaborating with customers, as well as common Agile practices.
For those new to Agile there is often an assumption made that the Scrum Master and the Project Manager are the same role.This is absolutely not the case. The two roles are very different and they each fit into approaches to projects that are wildly different as Agile is a Value and Culture driven Project Management Methodology.
I try to address some of the misunderstandings of the Scrum Master Role
You can see some of Scrum Master internal training videos that I did in past.
https://www.youtube.com/my_videos?o=U
How to Become an Indispensable Scrum Master
Kanban 101 workshop by John Goodsen and Michael Sahota. This is used to introduce Kanban and situate the workshop.
Please ask us if you would like PPT version.
Scrum is a framework for project management developed by Ken Schwaber and Jeff Sutherland. It is lightweight, simple, and difficult to master. Scrum uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like product backlogs and sprint backlogs. The goals are transparency, inspection, and adaptation. Scrum aims to deliver working software frequently through short development cycles and continuous improvement.
The mix of sessions for my first charity day[1]. For each timebox, we used poker to pick a themes then thumb voting to select the session.
[1] http://itstechupnorth.blogspot.com/2011/11/charity-days-spiking-coaching-mentoring.html
Lecture 2 from the MHIT 603 course on Human Interface Technology. This lecture provides an introduction to Prototyping. Taught by Mark Billinghurst at the University of Canterbury, July 17th, 2014.
The document outlines the process and milestones for a project between a client and Thoughtlab, including research, design, development, and launch phases over 12 weeks. It shows the tasks involved at each stage and lists deliverables such as personas, wireframes, UI reviews, MVP, testing, and launch. The timeline indicates the importance and client involvement for each milestone.
Scrum is an agile framework for managing product development that focuses on iterative delivery of working software in short cycles called sprints. It involves self-organizing cross-functional teams, prioritized backlogs to track requirements, and daily stand-up meetings. The goal is to rapidly and repeatedly deliver the highest business value in the shortest time through a flexible, holistic and collaborative approach.
The document discusses challenges with outsourcing software development and scaling agile frameworks. It recommends adopting both Lean and Agile principles to address challenges like long feedback cycles. Specifically, it suggests doing a Lean-Agile assessment, value stream mapping, and regular retrospectives to improve processes and focus on continuous delivery of business value. Patterns for successful distributed development include establishing global structures, rhythms, and practices to facilitate collaboration across locations.
Serverless Days Amsterdam - Choosing a Serverless Monitoring PlatformJosh Carlisle
油
- Logs provide deep diagnostics but can be a "haystack" that requires developer effort to find answers. Metrics give insights but complexity increases with correlation across systems. Tracing provides end-to-end visibility but gaps may exist.
- The three pillars of observability are logs, metrics, and traces. Avoid directly coding for monitoring to reduce technical debt and decrease visibility over time. Consider bytecode instrumentation to monitor without source code changes.
- Choosing a monitoring platform is difficult due to ephemeral compute, high distribution, and limitations of serverless platforms and cloud vendors. Look to logs for exceptions, metrics for baselines and AI, and traces for issues across upstream and downstream systems.
This document provides an overview of scrum and agile principles and practices. It discusses lean principles, the history and evolution of scrum, core scrum concepts like the product backlog, sprints, sprint planning, daily standups, reviews and retrospectives. It also covers scrum roles like the product owner and scrum master. Finally, it discusses topics like estimating, managing technical debt, requirements and user stories. The document serves as a comprehensive guide to scrum and agile concepts.
The document outlines an introduction to user experience (UX) design. It discusses what UX is, how it differs from user interface design, and provides examples of good UX. It then covers topics like wireframing, scenarios, paper prototyping and user testing to help workshop participants understand the UX design process.
Are Agile Projects Doomed to Half-Baked Design?theinfonaut
油
Today's web-based applications go live every few weeks. Agile methodologies like Extreme Programming and Scrum, focus on short development cycles, accelerated feedback from users and customers, and incremental delivery. On the technical side these approaches can bring discipline and predictability to short release cycles. But can these incremental methodologies incorporate successful design techniques? Using case studies and examples from their own project experience, Alex and Leslie will discuss how to integrate design and Agile, discussing what works, what problems arise, and most importantly, the changes in mindset that are necessary on an integrated Agile design/implementation team.
The document discusses interface design concepts and their relationship to business analysis and usability. It outlines eight golden rules of interface design including consistency, reducing memory load, and enabling shortcuts. It defines usability as the extent a product can be used effectively and efficiently to achieve goals. Business analysis should consider users, tasks, and context of use to incorporate elements of usability analysis.
This document outlines the roles, structure, communication, soft skills, and deliverables for a product team. It discusses key roles like product manager, UX designer, and UI designer. It describes different team structures such as centralized, integrated, and distributed. It emphasizes effective communication between designers and developers. Soft skills like growth mindset, empathy, and negotiation are discussed. Finally, it lists common deliverables from design research like personas and user flows to final outputs like prototypes, style guides, and usability test reports.
The document provides an overview of a UX workshop. It discusses key UX concepts like user experience design, personas, goals, tasks, information architecture, wireframing, paper prototyping, user testing and next steps. The workshop involves presentations, exercises and demonstrations on various UX topics. Participants will learn UX strategy and tools to design user-centered digital experiences.
The document provides an overview of a UX workshop. It discusses key UX concepts like user experience design, personas, goals, tasks, information architecture, wireframing, paper prototyping, user testing and next steps. The workshop involves presentations, exercises and demonstrations on various UX topics. Participants will learn UX strategy and tools to design user-centered digital experiences.
Scrum is an agile framework for managing product development that focuses on iterative delivery of working software. It involves short development cycles called sprints that typically last 2-4 weeks. Teams are self-organizing and work is planned and tracked using artifacts like a product backlog, sprint backlog, and daily stand-up meetings. The goal is to frequently deliver working, tested software to gain early customer feedback and continuously adapt to changing requirements.
Scrum is an agile software development method that uses short development cycles called sprints to iteratively develop products. Teams are self-organizing and work in sprints to develop and test software. Daily stand-up meetings are used to track progress. At the end of each sprint, working software is demonstrated to stakeholders. Microsoft uses scrum to quickly update products based on user requirements. Scrum allows for flexibility and adaptation to changing requirements.
Same Patterns Different Architectures - Colombo Architecture Meetup - Session-0399X Technology
油
This document discusses software architecture and design patterns. It begins by outlining key objectives like mapping business requirements to design patterns and understanding pattern relationships. It then defines concepts like object-oriented programming, design patterns, and software architecture. The remainder of the document discusses filling in the gaps between architecture and design, perceived understanding versus principles and patterns, and an example banking architecture with layers and modules.
Same Patterns Different Architectures - Colombo Architecture Meetup - Session-0399X Technology
油
Agile Placemat v9
1. ShuHaRi
Perspective
Mapping
Developed by Christopher Webb
Small
releases
Sprint
Planning
(1&2)
Product
Backlog
Sprint
Backlog
Poker
Planning
User Story
Daily
Meeting
Relative Estimation
Definition of Ready
3 qns
Burndown
Chart
Refinement
Meeting
Definition
of Done
Sprint
Review
(Showcase)
Retrospective
Task
Board
Limit WIP
Flow Control
Kanban board
Visual waste
& waiting
Make
Policies
Explicit
3 bin
system
Implement
feedback
loops
Frequent
releases
Evolve
experimentally
Muda,
Muri,
Mura
Story
Splitting
3Cs
INVEST
Story
Mapping
Personas Queuing
Theory
Manage &
Measure
Flow
Theory of
Constraints
Fast Feedback
Velocity
Lead
time
Optimal
Batch
Sizes
UML
Diagram
Risk Log
Minimum
Viable
Product
(MVP)
Minimum
Viable Change
Feature
Onsite
Customer
5 Whys 8 Wastes
5 Ss
Spikes
Design
Brief
Stakeholder
Mapping
Focal
Question
Relational
MappingTop 5 (ideas)
Business
Model
Canvas
Brainstorming
Rules of
Simplicity
Design
Principles
Low
Fiedelity
Prototypes
Doblins 10
types of
innovation
Define
Success
User
Testing
Walking
Skeleton
6 Levels of
Planning
Delphi
estimation
Product
Vision
(elevator
pitch)
Trade off
際際滷rs
Cause
effect
diagrams
Contract
Game
Project
approach
questionnaire
Storyboards
Facilitated
workshops
Scrum
of
Scrums
Story
telling
Guided
Tour
SPICE
2x2 Matrix
Feasibility
Assessment
Divergent /
Convergent
Thinking
Five Es
Why-How
Laddering
Programming
Rotation
Refactoring
Map
Revert
Independent
Goal Naively
Mikado
Dependency
Map
5
Focusing
Steps
TOC
thinking
process
Information
Radiators
Improvement
KATA
Dreyfus
Model
Team
eNPS
Actionable
Metrics
Monte
Carlo
Poisson
Cumulative
Distribution
Test Driven
Development
Integrated
Testing
Test
Automation
Inspections
7 qns of
context
driven
testing
Continuous
Integration
Automated Test
Code Coverage
Plant Types
Context
Driven
Testing
Reflection
Workshops
Domain
Object
Modelling
Niko-Niko
Calendar
Exploratory
360 degree
reviews
JIT
Ad-Hoc
retrospective Agile Release
Trains (ART)
Parking
Lot
Decision
Tree
Object
Relational
Mapping
Baselined
Requirements
Delivery
Plan
JIT Model
Storming
Continuous
Production Testing
Automated visual
dashboard
Continuous
Deployment
Standardised
Promotion
Path
Source
Code
Mgmt
Config
Mgmt
Virtualisation
Feature Toggling
Artefact
Mgmt
Version
Control
Dynamic
Environments
Componentised
Architecture
Automated
Build
Casual
Loop
Diagrams
Auto-scale & Heal
Buffer
Mgmt
Incremental
Architecture
Incremental
Re-architecture
Usability
Testing
Acceptance
Testing
Sustainable
Pace
Release
Planning
Story
Hierarchy
Metaphor
iterations Feedback
Loops
Test
Feature naming
template
Idea
collaboration
session
Ecosystem
Map
Empathy
Maps
Affinity
Clustering
Context
Mapping
Journey
Maps
PDCA
(Deming cycle)
Kaizen
blitz
Kaizen
burst
Refactoring
Document
Prerequisites
Change
Canvas
Scale
method by
colour
Osmotic
Communication
Reflective
Improvement
Focus
Period
(2hr)
SOLID
principles
4+1 View
architecture
Emerging
Design
(code
craftsmanship)
A3
Update when
if hurts
Team
Safe
space
Safety
(user
solution)
Business
Vision
Development
approach
definition
Time
box
Shift
Left
MoSCoW
Hypothesis
Statement
Value stream
mapping
Lean
Coffee
12 Cardinal Sins
Exploratory
Days
ADKAR Survey
4 MindsetsMarshall
Model
Mock Objects
Maricks
Test
Categories
Acceptance
Criteria
Understanding
complexity
(Framework
precedes data)
Sense making
(Data precedes
framework)
User
Case
CDEL
method
selection
Barmai
index
estimates
Improvement
Service
Communities
of Practice
System NFR
Overview
page
Feature
Teams
Potentially
Shippable Product
Overall
Retrospective
Requirement
Area
Feature Set (combined,
vertical, horizontal)
Product
Owner
Top down
+ Bottom
Up
Feature
team
adoption
map
Area
Product
Owner
Multi-team
design
workshop
Vision
Page
Team PBR
3 levels coaching (org, team, tech)
Organise
by
customer
value
Project
Charter
5 Dysfunctions of team
Strategic
Theme
ART
Budget
Release on
Demand
SAFe
Patterns
Program
Planning
3 Levels
Portfolio,
Program,
Team
WSJF Agile
portfolio
Architectural
runway
Portfolio
Backlog
Business EPIC
Innovation &
Planning
Sprint
Cycle time
Program
Increment
5Cs of
Agile
Mgmt
Architectural
EPIC
Release
Train
Engineer
Voice of
Customer
Cumulative
Flow
Diagram
Hackathon
4 versions
of lifecycle
Fixed
Delivery
Date
Software
Development
Context
Framework
(SDCF)
Hybrid
waterfall
practices
Product
Mgmt
Team
Architecture
Team
Geographically
distributed
development
(GDD)
Risk Value
Driven cycle
Coordinate
Activities
Focus
Goal
Diagram
Parallel
Independent
Testing
Tiger Team
Card sort
6
Sigma
Meddlers
(change
card game)
Delegation
Poker
Kudos
Cards
10
Intrinsic
desires
Moving
Motivators
Turn
up the
good
7 Tests
of a new
model
Schneider
Culture
Model
Theory X vs.
Theory Y
Collaboration,
Cultivation, and
Competence
Simple
Design
Business
Case
Solution
Architecture
Delivery
Control Pack
CRC Cards
Branching
Strategy
Leadership
FDD
Scaling
Initiate Discover Deliver Release
Disciplined Agile Delivery (DAD)Scaled Agile Framework (SAFe)
Large Enterprise
Scaled Scrum (LeSS)
Design Thinking
Cynefin
Lean
eXtreme Programming (XP)
Human Centered Design
Product Development (FLOW)
Deming Theory of Constraints
Dynamic System Development Method (DSDM)
RUP
Crystal
Mikado Method
Kaizen
Kanban
Rightshifting Management 3.0
Beyond Budgeting
DevOps
Test Driven Dev
Scrum
Prince2 /
Waterfall
Agile
Modelling
2016 Deloitte Consulting Pty Ltd.
The Agile Landscape v3
2. Common
Issues
Our
Process
Our
Offerings
Join Us
http://blog.deloitte.com.au/agile
We do agile evolution. Collaborating with organisations to disrupt their way-of-working,
thinking and delivery, with right-sized steps, a balanced approach, and tailored practices.
10+
GLOBAL
AGILE
NETWORK
ACROSS Countries
15+
MONTHLY
AGILE BLOG
PUBLICATIONS
Publications
BEYOND IT
STRATEGY &
IMPLEMENTATION100+AGILE
PROJECTS110
SCRUM
MASTERS, SAFe
& AGILE
CERTIFIED Practitioners
210AGILE
EXPERIENCE
Practitioners
Ideate
Agile mindsets and
collaboration
Agile business
case creation
Dont know
where to start
Design
Agile transformation
strategy and roadmaps
Process and operating
model design
Programme story
mapping
Tried agile
and failed
Experiment
Incubation hub
Growth hacking
Analytics, metrics
and insights
Safe BAU
experimentation
Cant
innovate
Deliver
Minimal viable change
Scrum masters and agile
specialists
Agile governance and risk
Education through delivery
Inefficient and
cant find value
Scale
Enterprise agility and organisational
change
Agile at scale. Agile evolution
Leadership and high performing
team enablement
Distributed agile
Agile PMO support
Complex
enterprise and
cant scale
Repeat
Maturity review and
change program design
Leadership and high
performing team
enablement
DevOps and release
engineering
Tool automation
Using agile,
but its costly
agile@deloitte.com.au
@DeloitteAgileAU
Agile