Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
#IWDev 11 - Requirements Gathering
Search
Matt Ball
May 07, 2013
Programming
1
75
#IWDev 11 - Requirements Gathering
How to maximise the bang-for-your-buck we gathering requirements.
Matt Ball
May 07, 2013
Tweet
Share
More Decks by Matt Ball
See All by Matt Ball
Build a Game: The @IWDev Challenge 2014
saxonmatt
0
120
Why I'll never be a Clojure dev
saxonmatt
0
220
Taking mutability out of the state machine
saxonmatt
0
590
Outside In: an introduction to TDD
saxonmatt
0
66
Other Decks in Programming
See All in Programming
AppRouter Panel Talk
yosuke_furukawa
PRO
1
470
効率化に挑戦してみたらモバイル開発が少し快適になった話
ryunakayama
0
140
障害対応を起点としたもっといい開発と運用のサイクル作りのためにできること / Hatena Enginner Seminar #29
polamjag
0
390
GraphQLサーバの構成要素を整理する #ハッカー鮨 #tsukijigraphql / graphql server technology selection
izumin5210
4
910
ServerAction で Progressive Enhancement はどこまで頑張れるか? / progressive-enhancement-with-server-action
takefumiyoshii
6
440
Kotlin Multiplatform at Stable and Beyond (Android Makers 2024)
zsmb
0
520
Native Federation: The Future of Micro Frontends in Angular
manfredsteyer
PRO
0
110
Elm 0.19.0 Changes
bkuhlmann
0
510
Documentation for users with AsciiDoc and Antora
ahus1
0
370
Amazon SQSコンシューマー疎結合への旅 - 出張! #DevelopersIO IT技術ブログの中の人が語る勉強会 #3
quiver
0
330
AWS CDKコントリビュートTIPS / aws-cdk-contribution-tips
gotok365
4
410
Ruby Pattern Matching
bkuhlmann
0
930
Featured
See All Featured
Stop Working from a Prison Cell
hatefulcrawdad
267
19k
Robots, Beer and Maslow
schacon
PRO
155
7.9k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
155
14k
Faster Mobile Websites
deanohume
300
30k
The Invisible Customer
myddelton
114
12k
Atom: Resistance is Futile
akmur
260
25k
Web Components: a chance to create the future
zenorocha
306
41k
Into the Great Unknown - MozCon
thekraken
15
1k
The Power of CSS Pseudo Elements
geoffreycrofte
62
5k
Imperfection Machines: The Place of Print at Facebook
scottboms
261
12k
Rails Girls Zürich Keynote
gr2m
91
13k
Designing for humans not robots
tammielis
247
25k
Transcript
Matt Ball, #iwdev 11 Requirements Gathering Getting the most !
for your $ Tuesday, 7 May 13
I’ve said it (here) before Building software is easy Tuesday,
7 May 13
...and this as well But it can be hard to
figure what you’re building Tuesday, 7 May 13
In fact Many people agree with this Tuesday, 7 May
13
Enough already! No more power phrases, please. (but lets keep
the pictures going, yeah?) Tuesday, 7 May 13
So why is it so difficult? Requirements Gathering is hard
Not enough time Stakeholder uncertainty Communication problems Tuesday, 7 May 13
Before all of that though, let me introduce you to...
Tuesday, 7 May 13
The four gnomes Gnome Gnomes Gnome Ungnomes Ungnome Gnomes Ungnome
Ungnomes Tuesday, 7 May 13
But wait! What is a good requirement anyway? Will deliver
measurable value Will identify any and all stakeholders Will be testable Seen it elsewhere? Copy it. Tuesday, 7 May 13
Not enough time Problems: Time is money. Full requirements and
specification takes lots of it. Tuesday, 7 May 13
Not enough time Solutions: Take an Agile approach to requirements:
Keep them lean Pictures User stories Examples Tuesday, 7 May 13
Stakeholder uncertainty Problems: User wants v.s. Business needs Broken processes
(don’t need I.T. bandages) Tuesday, 7 May 13
Stakeholder uncertainty Solutions: Ask questions Why do they want it?
Is it even an I.T. problem? Tuesday, 7 May 13
Communication problems Problems: Developers think implementation Testers think edge-cases Stakeholders
think £££ Tuesday, 7 May 13
Communication problems Solutions: Speak plain english (or whatever...) Review documentation,
always User stories Examples Tuesday, 7 May 13
!$ Maximize bang for your buck What if they were
all just 1 task? Requirements Conversation Documentation Testing Tuesday, 7 May 13
Gherkins! You knew they were coming, am I right? Tuesday,
7 May 13
BDD Behavior Driven Development: Developers, Stakeholders, Testers - in fact
anyone! Conversations and questions. Documentation in plain language we can all understand. Tuesday, 7 May 13
BDD Documentation: Features and user stories Scenarios and examples Concise
and lean Tuesday, 7 May 13
BDD Testability: Automated tests Validates correctness Validates value If you
cannot write a test for a requirement - you don’t understand it, or it isn’t one. Tuesday, 7 May 13
BDD Unseen benefits: Understanding, requirements, documentation and tests are always
in line with each other. Fragile tests indicate problems with a requirement. Transparency - for everyone. Tuesday, 7 May 13
Reading Tuesday, 7 May 13