Monday 28th September, 2015
2:00pm to 5:30pm
A guy comes to a doctor and says he needs a steroid inhaler for his bronchitis. The doctor asks 'Are you in any pain?' 'No, not really. A bit of pain in my leg, but I need the medicine for my bronchitis.'
'Any cough?' 'No.'
'Chest pain?' 'Yes, a little bit, I've already said I had bronchitis.'
'And why the leg pain? Did you injure it?'
'No, that doesn't matter. I stumbled and fell over, it's not a concern. There was some swelling and I grazed my chest at the same time.' 'So I understand that you have bruised your ribs? You don't need a steroid inhaler, just an ointment and some patience.'
Scrum or not-Scrum - patient's diagnosis is wrong or incomplete by default.
Scrum or not-Scrum - stakeholders forget who the product is for.
Scrum or not-Scrum - the most important this is: What for and Who for you are creating.
Scrum or not-Scrum - it's hard to remember it every day, the team tends to forget.
I will tell you - and teach you - how we bring out the customers all information we use to create the solutions they really need. It's not a single known method, and it's a little bit of each of them - it's my own mix of ideas and techniques, developed through practice of working with the customers. I will show you how to avoid building a product for stakeholders - even Scrum looks awesome, all holds up in the iterations, but still not for the users.
Beta tests stage is too late. From the very first day, your each move should be based on a clear, solid vision of the product and the business objectives. How to bring it out?
Chilid Web Design Agency CEO and Creative Director, visual stuff glutton, off-road driver
Sign in to add slides, notes or videos to this session