Customer Driven Requirements

Art of driving great outcomes and not just designing the solution in a pretty format

Lean * Agile = Exponential Opportunity Business Strategy, product roadmaps, development to feedback – everyone is accountable for their input into the

quality and outcomes of the delivery stream

Strategy

Portfolio

Product

Release

Iteration

Daily

Strategy

Portfolio

Product

Release

Iteration

Daily

Lean Business Values 1. Identify Value 2. Map the Value Stream 3. Create Flow 4. Establish Pull 5. Continuously Improve

Strategy| What business do your customers think you are in, what do they expect?

“If I’d asked customers what they wanted, they would have said ‘a faster horse’.”

Henry Ford

Strategy

Portfolio

Product

Release

Iteration

Daily

Market Driven Catalogue 1. Understood 2. Responsive 3. Adaptable 4. Continuously Evolving

Tactical| Either innovating and creating a market disruption or your responding to it

Cost of servicing the problem

• Customer Service Centre

• Maintenance Technicians

• Guarantees / legal

• Postage

• Packaging

Handymen kept cutting the power cord, Bosch kept ‘servicing’ the fault to be the best in customer service

Cost of Dissolving the problem

• $0 for Bosch

• The handyman replaced the cord he cut in 5 min

• As a powered saw I want to be long enough to be hooked to a ceiling so that I don’t get cut

• AC =

• 3m long power cord

• Reinforced rubber at hook point

• S hook provisioned in packaging

Cost of not driving innovative outcomes

• As a handy man I want as little downtime to repair my saw when the cord is cut so that I can get back to doing paid jobs

• AC =

• Fix in under 30 min because I can’t afford not to work

Strategy

Portfolio

Product

Release

Iteration

Daily

User Driven Requirements What is the outcome & why

1. Business Value 2. Business Pain 3. Delivery Risk 4. Relative Estimation

Driving Value| Are you selling what the customer will value or what you think they want

User Story | Structure

As a....who, what role, what client,

I want....what outcome, achieve what, what artefact

So that... Why, what’s the point, what value do you gain

Acceptance Criteria ... I will deem your delivery successful if

• You meet this condition...

• Deliver this metric...

• provide with...

• Ensure that...

Priority.....relative weighting to facilitate order of importance

Business Value | Business Pain | Complexity | Magnitude

User Story | Requesting Customer Value into work packages

User Story | Difference between Theme, Epic, and story?

Standard codes of practice | User Stories are only as good as the environment & principles that it’s delivered in

As a....human with a family I want....a house so that... I don’t get rained while I'm asleep, I'm warm when the wind blows and I can watch my huge flat screen tele

Acceptance Criteria ... I will deem your delivery successful if

• Provide electricity & electrical outputs

• Wood window frames

• The roof has 0% precipitation

• The inside is sealed

Guides of practice | Knowledge Management Working Software over comprehensive documentation

• Continuous team builds on it’s inherent knowledge

• Don’t document for history, share knowledge for use, for a user

• Keep the knowledge “As close to the user as possible”

• ‘Reference Knowledge – don’t rewrite specification for each new requirement – i.e. Test Automation Repositories will store, and run according to standards set. Java Coding Style 8.1

@ min 80% code coverage

– GUI must be legally valid according to at minimum WCAG 2.0 Priority 1 & 2

• Does a user guide need to be a second implementation of the software or is the software the guide (often a quick assessment of how ‘user friendly’ your software is by how big you need the training or support documentation to be)

Start playing with stories| exercises to try

• Create User Personas – get to know who

• Definition of Done – starting collation point for all those standards to be met

• Interview your colleagues & customers –

– what’s the top 5 most awesome outcomes you could have and why?

– If I built a prototype what’s the minimum you’d deem it good enough to beta with customers?