Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Agile Requirements, Successful Agile Projects

BA World 2010 presentation in Melbourne Australia
by

Matthew Hodgson

on 1 August 2017

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Requirements, Successful Agile Projects

How could I
measure
success?
that
but what's your
experience?
What would make my project
successful
Over 35 documents / deliverables
Still deliver the full scope of requirements
Still required to plan, analyse, design, code, test and deliver

... it's something we've all experienced
Requirements
understood
documented
agreed
signed-off?
Requirements elicitation
agreed/signed-off
requirements
by sensei & client
Let's add more deliverables!
Hmmm, we're not delivering enough value for the first
3 months
contract negotiations took longer than expected
4 months became
8 weeks
The problem
Lots of previous #FAIL by others in the project environment
High risk environment
High expectation of auditability of project actions & decisions
Demand for PRINCE2 project governance
Other issues
with this way of working?
to communicate success measures to the client
to ensure success could be replicated later
Project delivered:
on time
on budget?
Implement a system that manages training documentation:

Internet/extranet
SharePoint 2010
Workflow & version control
Document management
4 months to complete
Tends towards:
Less structure
Shorter iterations
Focus on communication
Better adaptable to change
Tends towards:
More structure
Longer iterations
Focus on process
Less adaptable to change
I didn't have to choose Waterfall
Isn't that just RUP?
That's just an
excuse to do no
documentation
Another name
for
"Cowboy Coding"
We tried it
before and
it didn't work
It won't work here.
We're different.
Elvis is alive
UFOs are real
Bigfoot does exist
Salmon shirts are not pink
Waterfall Project Mgmt is best-practice
Upfront planning & design lowers risk
But people believe in lots of things ...
Forrester research
Agile is 'mainstream':
Scrum - 10%
Agile Modelling - 6%
Feature-Driven Development (FDD) - 3.8%
Test-Driven Development (TDD) - 3.4%
eXtreme Programming - 2.9%
Lean development - 2.1%
Microsoft Solutions Framework for Agile - 1.8%
Agile Data Method - 1.6%
Adaptive Software Development - 1.3%
Crystal - 0.3%
Behaviour-Driven Development (BDD) - 0.2%
Dynamic Systems Development Method (DSDM) - 0.2%


Less reliant on:
Use Cases
Upfront requirements specification
Focusses on:
User Stories and scenario-based requirements
Modelling, prototypes and diagrams
working
A different way of
SCRUM + Lean + ISO13407 + UCD
SMS coaches this framework
Our chosen framework
Breaking down the scope
Sprint 1
User login
Registration
Security
Sprint 2-3
Data collection
EDM
Workflow
Sprint 4
Public website
project
DNA
project
DNA
project
DNA
4 sprints x 2 weeks each
project
DNA
things to produce
things to do
skills to apply
patterns
to apply
storyboards
wireframes
process maps
prototype
identify business rules
SharePoint 2010
user experience
information architecture
analysis
web security
spike solution
'clear the fog'
this is really just speculation!
things to do
things to produce
'just enough' documentation to communicate to the client
list of users & roles
list of activities undertaken from users' perspectives
list of business outcomes wanted

Workshop outputs
As a system manager
I want to admin
user a/c
in order to adhere to
sys security reqs
As an author I want to
see what's going on in
the system so I can
prioritise my work
Story Cards
persona
activity
outcome sought
As an author I want
to see my works in
progress so I can
remember what I
was last working on
requirements prioritisation
UCD + collaborative design
user/business ranking of requirements priorities
Sprint planning
kanban
Project management w/
Requirements documentation
team
communications
board
task
visualisation
& tracking
replace your Gannt charts!
As an author I want
to see my works in
progress so I can
remember what I
was last working on
As a system manager
I want to admin
user a/c
in order to adhere to
sys security reqs
As an author I want to
see what's going on in
the system so I can
prioritise my work
stored and tracked in
deposited and shared thru
automated reporting
captured project board decisions and approvals
SOX compliant
Situational formality & auditing
agreed by client & sensei
TDD
Sign-off
Success measures
visualise the value-chain
report velocity
identify road blocks
identify over/under estimation
Benefits
enables conversation on WIP w/ the client
immediately identify priorities
enable just-in-time changes to WIP
Lean - assists identify and eliminate waste

Benefits (cont.)
Delivered value
Delivered working code
Delivered rationale for requirements/specs
Documented what was created, rather than what 'might' be created
Input new ideas
Helped re/prioritise requirements
Helped us adapt and change to new requirements/needs
Every two weeks...
Client got to...
Retrospectives ...
What did we do well?
What didn't we do well?
What do we need to change now to do better?
learn & adapt now rather than waiting til the end of the project!
Things we did well
Not so good
Need to change?
Get the developer colocated
Focus on the sprint
Sprint 2wks 1wks
Some tendencies to focus on understanding the 'whole' solution first, rather than just the sprint at hand
Team cohesion good
Adapted to scenario-based requirements
learning from experience
high-value incremental delivery
Adjusted the board at Stand-ups
Personas
Value & success?
objective
involvement
ownership
buy-in
integrated change mgmt
lean - clear value pipeline

task
tasks & stakeholders being engaged
test/validate (prototype & TDD)
develop solution
deploy
requirements (A3s/epics)
context (storyboards)
team members
next highest priority tasks
backlog
stakeholders to engage
Total of 112 MB of documentation!
Documents delivered:
Document_3_Functional_Requirements_Specification11.doc
Document 10_Support Framework.doc
Document 9_Test Strategy.doc
Document 8_Training Design Scope.doc
Document 5_Technical Design.doc
Document 5_Technical Design Appendix C.doc
Document 5_Technical Design Appendix B.doc
Document 5_Technical Design Appendix A.doc
Document 2_Business Requirements.doc
Executive Summary_FINAL.doc
Data Migration and Document Transformation Strategy_01.00.doc
Change Management_01.00.doc
Document_4_Information_Architecture.zip
Proof of Concept system
What went wrong?
scenarios
architecture
SharePoint 2010
functionality
IA &
user req.
business req.
system req.
a disconnect started to appear
I got sick!
Where's
all the deliverables?!
We must
re-focus on documentation!
... they got a PM in to replace me
delivering documentation
delivering value
Conclusions
The team had to change the way it worked
No more "analyse everything until you’re happy/comfortable"
Driven by user value - not what we thought might be good or cool
Adapting to working in 1-2 week iterations
Taking responsibility for delivering working code
Self direction - having no one tell you what/how to do
Agile is fun, but it's also hard!
Faster way of working
Different way of working
More efficient, 'Lean' way of working
Reinforced visualisation of work and outputs
Increased team communication
Decreased reliance on documentation
Created a dynamic, exciting working environment

Ultimately:
Need good communication to be Agile
Change of 'success paradigm'
What the team experienced
What the client experienced
Faster way of working
Different way of working
More efficient
Greater buy-in
Integrated change management
More communincation - you know whats going on, when and why
Greater transparency
More influence - you CAN change tact when you need to!
You can adapt to change rather than trying to 'control' it
successful agile projects
My project experience
The problem
The scope
Project approach
workflow breakdown
Storyboards
Agile = reinforcing collaboration
Rather than
working in isolation
working on the whole problem
integrating solutions later
changes to
The Waterfall Way
The Agile Way
Agile - deliver value over documentation, adapt rather than blindly following a plan
Lean - reduce waste thru the project
UCD - increase buy-in from users
ISO13407 - scenario & context drives better requirements
The Team?
Most experiencd BA w/ client relationship as Scrum Master
Business BA as the Product Owner
The Samurai
The Sensei
Members chosen based on the Project DNA
Look Ma!
No PM!
SMS Management & Technology
M +61 404 00 66 95
E magia3e @ gmail.com
W zenagile.wordpress.com

Twitter @magia3e
Senior Agile Coach
Agile Samurai

How can I be Agile?
Follow the Twitter #agile conversation
Get an Agile Coach to help with your first project
Read blogs on Agile –- zenagile.wordpress.com
Read books on Agile – the Art of Agile Development (James Shore)
Start with a small project, then work your way larger
And …
It’s ok to apply agile principles in Waterfall
#FIN
How can I ask for Agile?
Put into the Statement of Work:
Your project's DNA
Ranked priority of User Stories
Fn/Non-Fn reqs for those User Stories
Your need for a flexible backlog
Identification of what the vendor will deliver in a 'skinny solution'
Costings for the 'skinny solution'
Delivery of the 'skinny solution' in 8 weeks
A preference for Agile, UCD and Lean approaches
It requires a lot of discipline to work this way!
Value and burn-up
How to work in parallel?
But I can't use these methods!!!
What I've found:
Clients either love them or hate them

To make these deliverables work:
Involve the business in their creation
Involve the business in their iteration
and improvement
Then they become not YOUR work, but THEIRS
Emphasis on working:
collaboratively
simultaneously
in parallel
on smaller pieces of the puzzle
=
/
Business requirements

user needs
collaboration broke-down
focus on ACT vs. Sydney lines of communication
The result
Personas
Storyboards
A3s / Epics
automation thru forms
user-
prioritised
features
story
card
acceptance
criteria
working
code
Started with:
Finished the project:
"Some things in life you can't learn from books, study or accademic discussion ..."

"You must experience them"
agile requirements
Full transcript