Design thinking, Agile. How to cook it as lean startup.
•
1 like•242 views
Modern times require smarter approaches for creating software products. Extremely high competitive environment and global economy need us to be fast and responsive to prevent failures. There are a lot of practices in management, engineering and design were invented for the last decades. We shall discuss how to combine such things like Design Thinking, Agile, lean approach, proper technologies, and smart team for organizing the most effective development process for a startup.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Design thinking, Agile. How to cook it as lean startup.
Similar to Design thinking, Agile. How to cook it as lean startup. (20)
Recently uploaded
Recently uploaded (20)
Design thinking, Agile. How to cook it as lean startup.
- 1. Design Thinking Agile How to cook it as a lean startup Oleh Korkh CTO, The7bits and CL the7bits.com crane-locator.com
- 4. – Wikipedia about Lean Startup “Lean startup is a methodology for developing businesses and products, which aims to shorten product development cycles and rapidly discover if a proposed business model is viable.”
- 6. Key points • Design Thinking • Agile • Proper Technologies • Clever Team
- 7. Design thinking Design thinking is a non-linear, iterative process which seeks to understand users, challenge assumptions, redefine problems and create innovative solutions to prototype and test. The method consists of 5 phases — Empathize, Define, Ideate, Prototype and Test and is most useful when you want to tackle problems that are ill-defined or unknown. https://www.interaction-design.org/literature/topics/design-thinking
- 8. Empathise Author/Copyright holder: Teo Yu Siang and Interaction Design Foundation. Copyright licence: CC BY-NC-SA 3.0 Credits: https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process
- 9. Define
- 10. Ideate
- 11. Prototype
- 12. Test
- 13. Design Thinking
- 14. Agile Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan https://agilemanifesto.org
- 15. Scrum, Kanban? Particular process is not a goal. Flexibility and comfort are important.
- 16. Technologies Rapid development is a key
- 18. #NoEstimates Be flexible and do not estimate in hours Credits: https://blog.magnusdahlgren.com/2017/03/23/noestimates-just-story-points-done-right/
- 20. Conclusion • Do not concentrate much on the original idea • Iterate, do not think much with roadmaps • Be ready for changes • Be responsive • No over detailed plans, update priorities and forecast • Use technologies which are suitable for rapid development • Vision-, trust- and empathy-driven process