10. Reviewing
1. product / market fit.
1. quickly build your idea
1. release, manage and scale up your idea.
1. Lean Startup and Design Thinking
1. Some form of Agile Software Development
for building your idea
1. DevOps for releasing and managing it in
production.
Blog “extreme uncertainty” http://sumo.ly/kF22
11. Reviewing
1. product / market fit.
1. quickly build your idea
1. release, manage and scale up your idea.
1. Lean Startup and Design Thinking
1. Some form of Agile Software Development
for building your idea
1. DevOps for releasing and managing it in
production.
Blog “extreme uncertainty” http://sumo.ly/kF22
12. Reviewing
1. product / market fit.
1. quickly build your idea
1. release, manage and scale up your idea.
1. Lean Startup and Design Thinking
1. Some form of Agile Software Development
for building your idea
1. DevOps for releasing and managing it in
production.
Blog “extreme uncertainty” http://sumo.ly/kF22
13. Wikipedia
Agile practices
Agile development is supported by a bundle of concrete
practices, covering areas like requirements, design, modelling, coding, testing, project
management, process, quality, etc. Some notable agile practices include:
...
User Story Mapping
https://en.wikipedia.org/wiki/Agile_software_development#Agile_methods
19. KPIs - the compass
If we will make progress towards the product goal, how we will know it ?
20. Cards, Conversation, Confirmation
Goal clear after discovery and tests
1)Title, Who, What, Why (As... I want... So that...)
Talk to understand details
1)Additional details, sketches, etc.
2)Acceptance criterias (how do we know that the story is done)
21. Building the User Story Map
Silently write down the user tasks based on the current common understanding
and stick on the wall.
Name what you might build - avoid saying how - Jeff Patton
Kent Beck first introduced the term as part of Extreme Programming to encourage a more informal and conversational style of requirements elicitation than long written specifications.
Kent Beck first introduced the term as part of Extreme Programming to encourage a more informal and conversational style of requirements elicitation than long written specifications.