ICONUK 2015: Zen and the art of requirements gathering, why getting to "In time, On budget and In scope" is easier if you start out right

UKLUG 2012 – Cardiff, Wales
My Session Name
Warren Elsmore
Zen and the art of requirements
gathering
September 2012
Why getting to “In time, On budget and In scope” is easier if you
start out right
Presenter: Femke Goedhart & Tim Clark

•Business Consultant
•Ipsamet Consulting | Silverside
•@FemkeGoedhart
•http://femkegoedhart.com
About us….
Tim Clark Femke Goedhart
• Director of Prof. Services
• Teamstudio
• @TimsterC
• http://tc-soft.com

And now for something completely
different…

Roleplay #1

My Session Name
Warren Elsmore5#engageug

10 Cosmic truths about
requirements gathering
From
‘More about software requirements’ by Karl E. Wiegers
More about Software Requirements 2006, Karl Wiegers

#1: If you don’t get the requirements right,
it doesn’t matter how well you execute the
rest of the project

Development Work
Developmen
t
60%
Rework
40%
Shull et al. 2002, GAO 2004

Influence Of Requirements On
Rework
Rework
40%
Other
25%
Leffingwell 1997
Requirement
Errors
75%

#2 Requirement development is
a discovery and invention
process, not just a collection
process

Expectation Gap
Time —>
Expectation gap
Software Requirements third edition, Karl Wiegers & Joy Beatty

Time —>
Expectation gap
touch pointtouch point

Cone of uncertainty
Boehm 1981

#3 Change happens
(so does sh*t)

•Get sign off, before you move on
•Manage the refinement of requirements
•Change management process for RFCs

Start With The Why
Vision & Scope document
User requirements document
Software requirements specification
WHY
HOW
WHAT

Increasing Levels Of Details:
Vision & Scope document
User requirements document
Software requirements specification
Business
requirement
Business
rules
User
requirement
Quality
Attribute
External
interfaces
Functional
requirement
System
requirement
Constraints
Non-Functional
requirement

1x
Cost Of Rework

1x
Cost Of Rework
5-10x

1x
5-10x
100x
Boehm 1981; Grady 1999; Haskins 2004
Cost Of Rework

•So do you really need an RFC process ???

Roleplay #2

#4 The interests of all
stakeholders intersect in the
requirements process

Analyst
Other
Stakeholders
Customer
User
Developer
Tester
Project
Manager

Office politics – org chart
Influencers
Decision
Makers
Sponsor Fred
Jones
Tamsin
Smith
Rajesh
Patel
Alma
Simmons
Nigel
Falstaff
Finlay
McDonagh

• Direct users
• Indirect users
• Stakeholders
• Sponsors
• Acquirer
• Management
• Compliance auditor
• Suppliers
• Regulatory body
• Quality assurance
• Etc, etc…….
Who will use it?
Who will depend on it?
Who has a stake in it?
Who will own it?

#5 Customer involvement is the
most critical contributor to
software quality

•Identify user classes
•Select product champions
•Build prototypes
•Agree on customer rights & responsibilities

#6 The customer is not always
right, but the customer always
has a point

•Be critical, play devils advocate
•Be open
•Be realistic
…..and get the customer to see reason

Roleplay #3

My Session Name
Warren Elsmore33#engageug

?

!

https://www.youtube.com/watch?v=OmCxtWrRQJ8

#7 The first question an analyst
should ask about a proposed
new requirement is,
“is this requirement in scope?”

Context diagram
Cafeteria
Ordering
System
Menu
Manager
Patron
Order
Process
Meal
Deliverer
Payroll
System
DeMarco 1979, Karl Wiegers 2003

MOSCOW
Requirement M S C W
Insert multiple order lines x
Create an export of closed orders x
Allow to copy order details to
allow quick registration
x
Allow for inserting personal notes
on orders
x

MOSCOW
Requirement Costs M S C W
Insert multiple order lines $ 100 x
Create an export of closed orders $ 1500 x x
Allow to copy order details to
allow quick registration
$ 250 x
Allow for inserting personal notes
on orders
$ 100 x x

EISENHOWER DECISION
MATRIX
Urgent Not Urgent
Important
Crises
Deadlines
Problems
Relationships
Planning
Recreation
Not Important
Interruptions
Meetings
Activities
Time Wasters
Pleasant
Activities
Trivia

PRIORITISE
Urgent Not Urgent
Important Must! Should
Not Important Could
Won’t
(Nice to have)

#8 Even the best requirements
document cannot – and should
not – replace human dialogue

#9 The requirements might be
vague, but the product will be
specific

Make it “SMART”
• Specific
• What? Why? Who? Where? Which?
• Measurable
• How much? How many? Is it quantifiable?
• Attainable
• Can it be achieved with the resources & facilities available?
• Relevant
• Does it relate to the project vision & scope?
• Timely
• Can I set a date to it?

A picture is worth more than a 1000
words
Requirement
The current solution that Xxxxx have created in the Xxxxxxxx, XX depot is that they complete a spreadsheet that is shared across all members of the depot. This is effective but is a lot of work to enter all data for each delivery or collection. It’s also dependent on
each driver having a smartphone with a data connection to access the Google spreadsheet while out at each delivery/collection site. The photos that are currently brought back are then uploaded at the office and there is a final task to match the photo with the
delivery record.
The requirement is to have a system for the depot dispatcher to be able to assign jobs to each truck for the day and also be able to assign ad-hoc deliveries or collections while the driver is out on their route.
The drivers needs to be able to select which truck they are assigned to and then see the jobs that are assigned to that truck. Once they have arrived at the delivery site, they need to be able to take photographs of the site as they arrive, the materials delivered to
site and then the site as they leave. Also the ability to capture a signature and receiver’s name or to record that there was no one on site to receive the delivery.
Solution
The proposed solution is that there will be two streams of development but a single Notes/Domino .nsf for each depot. One stream will be for the dispatcher side of the application and based on a desktop browser and one for the driver’s version of the application
that will be capable of running in Teamstudio Unplugged on iPhone or Android mobile devices. The dispatcher’s screen would be able to take a delivery schedule item and place it onto a truck’s route. The system would know the gross weight of each delivery and
the max laden capacity of each vehicle and therefore not allow any one truck to be over loaded. Each driver will be able to readjust the delivery schedule based on his/her local knowledge of the route and be able to drag and drop each item on their route
schedule. Once the driver has delivered their goods they can update the dispatcher by running a sync of the system so that the central database is updated with the collected information. The driver starts the process by selecting which vehicle they are assigned
to and then gets to view the deliver schedule. Once they have organized it to their liking the driver can set off to the first delivery. At the delivery the driver clicks on the job card and is asked to take a photo of the scene to record the original state of the delivery
environment. Once the goods have been delivered to site then the driver can take another photo to record the good on-site. He/She can then gather a delivery signature from the person receiving the goods or just click ‘No Signature’ if there is no one there. Just
before leaving the driver takes a last photo and to show the delivery environment after the delivery has been made to prove that no damage has been caused during the time of delivery. This is all sent back to the controller so that they have an understanding of
the delivery status and the site status before, during and after delivery. The Dispatcher also knows how far along he schedule his driver is at any given point. They also have all the information required should a customer call to question a delivery status or goods
left by the driver.
The sketches that follow are Teamstudio’s concept images for this application and will be subject to change when discussed with the customer during the initial phase of the development project.

#10 You’re never going to have
perfect requirements

Questions ?

Bibliography
•Software Requirements (Third Edition)
Karl Wiegers & Joy Beatty
ISBN: 978-0-7356-7966-5 (Microsoft Press)
•More About Software Requirements (Best Practices)
Karl Wiegers
ISBN: 978-0-7356-2267-8 (Microsoft Press)
•Mockup tool: http://balsamiq.com/

ICONUK 2015: Zen and the art of requirements gathering, why getting to "In time, On budget and In scope" is easier if you start out right

Recommandé

Recommandé

Contenu connexe

En vedette

En vedette (8)

Similaire à ICONUK 2015: Zen and the art of requirements gathering, why getting to "In time, On budget and In scope" is easier if you start out right

Similaire à ICONUK 2015: Zen and the art of requirements gathering, why getting to "In time, On budget and In scope" is easier if you start out right (20)

Plus de Femke Goedhart

Plus de Femke Goedhart (20)

Dernier

Dernier (20)

ICONUK 2015: Zen and the art of requirements gathering, why getting to "In time, On budget and In scope" is easier if you start out right