Embed Size (px)
DESCRIPTION
A practical pragmatic demonstration on how to use Agile in environments where scope and schedule are apparently fixed.
Citation preview
AGILE IN HIGHLY REGULATED ENVIRONMENTS ALASTAIR BROWN, HEAD OF DELVIERY
CONSTITUTES OR CONSTRAINS RIGHTS
ALLOCATES RESPONSIBILITIES
GOVERNMENT AUTHORITY
SELF REGULATION
CO-REGULATION
MARKET REGULATION
REGULATION
WHAT IS IT?
Influence an outcome
Prevent a market failure
Reach a collective desired
outcome
Implement legislation
REGULATION
WHY?
THE BUSINESS GOALS // WHAT I NEED IS…
• high quality
• schedule control
• cost control
THE REGULATORS GOALS
• “fixed” scope
• fixed schedule
• specific features
(…but these are usual aspirations,
regulated or not)
REGULATION
GOALS
SO MY DEVELOPMENT APPROACH NEEDS…
SERIAL PROCESS
DELIVERY LIFECYCLE
SERIAL PROCESS
GATED ENTRY AND EXIT
SO MY DEVELOPMENT APPROACH NEEDS…
DELIVERY LIFECYCLE
SERIAL PROCESS
GATED ENTRY AND EXIT
DOCUMENTATION REVIEW AND SIGN OFF
SO MY DEVELOPMENT APPROACH NEEDS…
DELIVERY LIFECYCLE
SERIAL PROCESS
GATED ENTRY AND EXIT
DOCUMENTATION REVIEW AND SIGN OFF
HIERARCHICAL GOVERNANCE
SO MY DEVELOPMENT APPROACH NEEDS…
DELIVERY LIFECYCLE
SERIAL PROCESS
GATED ENTRY AND EXIT
DOCUMENTATION REVIEW AND SIGN OFF
HIERARCHICAL GOVERNANCE Long Term
Detailed Plan
SO MY DEVELOPMENT APPROACH NEEDS…
DELIVERY LIFECYCLE
SERIAL PROCESS
GATED ENTRY AND EXIT
DOCUMENTATION REVIEW AND SIGN OFF
HIERARCHICAL GOVERNANCE Long Term
Detailed Plan
SO MY DEVELOPMENT APPROACH NEEDS…
DELIVERY LIFECYCLE
SO WHAT I NEED IS…
DELIVERY LIFECYCLE
SO WHAT I NEED IS: Cost and schedule control
DESIRED OUTCOMES
CONTROL COST AND SCHEDULE
• BACKLOG MANAGEMENT
• SCOPE NEGOTIATION
CONTROL QUALITY
• CONTINUOUS INTEGRATION
• TEST DRIVEN DEVELOPMENT
• MEASUREMENT OF COVERAGE, CODE QUALITY
BUT HOW… Agile 101
DESIRED OUTCOMES
Focus on Business value
Embrace changing requirements, understand impact
Frequently and regular delivery
Performant motivated teams, provide the tools and remove impediments
High bandwidth interaction between Business people and Developers
Inspect, learn and adapt
Self organisation
Sustainable development pace
Simplicity
Progress Measured by working, delivered, accepted software
VARY RICHNESS
PRIORITISE
HOW?
FIXED SCOPE CONUNDRUM
SUD
Operations
Customer Support
CFO Analyst
Marketing
Sales
CSO
Regulator
USERS AND STAKEHOLDERS
FIXED SCOPE CONUNDRUM
… BUT DON’T FORGET THE REGULATOR (OR PROXY)
USER AND STAKEHOLDER STORIES
FIXED SCOPE CONUNDRUM
“As the CSO I would like data to be
separated from the application in a
data vault so that I can comply with
PCI DSS guidelines.
As a WebMaster I would like the user
to fill out a CAPTCHA field so that I
can be sure the user is human and
avoid spam.
UNDERSTAND THE PRIORITY OF GOALS
FIXED SCOPE CONUMDRUM
COMPLIANCE
COST REDUCTION
REVENUE PROTECTION
REVENUE GENERATION
UNDERSTAND THE PRIORITY OF GOALS
FIXED SCOPE CONUMDRUM
REVENUE GENERATION
COST REDUCTION
REVENUE PROTECTION
COMPLIANCE
USE TO HELP PRIORITISE
FIXED SCOPE CONUNDRUM
LARGE SCALE – Three projects – 100 staff 18 months
PUBLIC SECTOR – Social Security domain
SYSTEMS INTEGRATOR – CMMI Level 5
HISTORY OF BUDGET AND SCHEDULE OVERRUN – Requirements ambiguity
– Incomplete
– Poor quality
HEAVY QMS DESIGNED FOR WATERFALL
CONTEXT
THE CASE STUDY
PRODUCT OWNER
SCRUM MASTER
SCRUM TEAMS
RELEASE/ITERATION CFD
QUALITY PRODUCT BACKLOG
PRIORITISED BY STAKEHOLDER
BSG CATEGORISATION
HIGH VISIBILITY IMPEDIMENTS
SPRINT VELOCITY
UNIT TEST
RETROSPECTIVES
DEMONSTRATION
SO WHAT DID WE DO?
THE CASE STUDY
SPRINT AND RELEASE CFD – fed RAG and morning prayers, schedule reviews, change board and improved visibility.
DAILY STANDUPS – Fed the risk review board
UNIT TESTING – Became the “sign off” artifact for the sprint
DEMONSTRATION – Made UAT self fulfilling
PRODUCT OWNER – Fulfilled the communication plan
WHAT WAS THE OUTCOME?
THE CASE STUDY
RELIABLE/REPEATABLE OUTCOMES
SHOW ACCOUNTABILITY
DEMONSTRATES DUE DILIGENCE
DELIVER HIGH QUALITY
REGULATOR ASPIRATIONS
AGILE IN HIGHLY REGULATED ENVIRONMENTS
AGILE CHARACTERISTICS
AGILE IN HIGHLY REGULATED ENVIRONMENTS
MANAGED REPEATABLE
DEFINED CONSISTENT PROCESS
QUANTITATIVELY MANAGED
ADAPTIVE AND OPTIMISING
HANG ON….
AGILE IN HIGHLY REGULATED ENVIRONMENTS
Level 1 - Ad hoc (Chaotic)
– Typically undocumented process
– Unrepeatable often relying on heroics
– State of dynamic change in an uncontrolled and reactive manner
Level 2 – Managed Repeatable
– Some processes are repeatable possibly with consistent results
– Limited rigour, although processes usually maintained during times of stress
Level 3 - Defined
– Defined and documented standard processes established
– Delivering consistency across the organisation
– Some degree of improvement
Level 4 – Quantitatively Managed
– Use of process metrics allows for control of the process
– Ability to adjust and adapt the process to particular projects without measurable losses of quality or deviations from specifications
Level 5 - Optimising
– Focus on continually improving process performance through both incremental and innovative technological changes and improvements
Understand your current position and aspirations; plan and action your first next step, then Inspect and Adapt
Be as Agile as you are (currently) able; within your (any) current constraints
Do not assume that your constraints prevent the implementation of Agile practices
Do not prepare the barrel for the Waterfall
CONCLUSION
AGILE IN HIGHLY REGULATED ENVIRONMENTS
?
ANY QUESTIONS …
