140 likes | 264 Views
And now for something completely different. Does the bit in the middle really matter?. o r; If you can manage requirements and match them to successful UAT - is that all you really need to do?. First sort out the requirements or ; Who thought this up anyway?. What are we trying to achieve?
E N D
Does the bit in the middle really matter? or; If you can manage requirements and match them to successful UAT - is that all you really need to do?
First sort out the requirements or; Who thought this up anyway? • What are we trying to achieve? • How many ‘bells & whistles’ do we really need? • How fast does it have to go? • Is security an issue? • Which bits will cost us the most if they break? • When do we need it by?
UAT or; Who is the customer? • What are we trying to achieve? • What happens if I push this? • Is it fast enough? • Can I break it? • Does it do what I need for now? • How long can I wait for it to be better?
What was that bit in the middleor; How do we test this thing? • Have we done this before? • Can we do this at all? • How hard is it to do • Will we need to this again (and again)? • How should we keep track? • Who fixes stuff and how do we tell them? • What else do we need? • How do we know when we’re done?
How do we get from requirements to UATor; What do we really have to do? • Plan not to do anything twice • List what to do and record what you did • Only do what you must do • Accentuate the negative and the positive • Never assume a fix is fixed • If it’s too hard, it probably won’t work • Evidence is king – You are not the judge
A conclusionor: This isn’t really the end So of course the middle is important and an opportunity to cut cost & speed delivery But to cut risk – Requirements & UAT are the key!
The End Thank you paul.rolfe@thinksoftglobal.com www.thinksoftglobal.com info@thinksoftglobal.com