When you want to discover many solutions to a problem
When you want to split a solution into user stories
When there is a blocker with the legal team
When a feature you have tested is not working
When you do not understand how the product work
Devs only care about what they should build
True
False
What sections should you add in a project kickoff document?
Screens of the solution
Segment of users impacted by the problem
Verbatim of users related to the problem
Past technical analysis around the solutions
How your competitors are solving the issue
Why are solving this issue?
User stories priority
Why should you care about your standups?
It helps me understand how the project is going
It helps me having a nice time with my team
It helps me discover tiny issues dev could face without knowing about it
It allows developers to debate about a technical decision
It allows me to communicate to the team changes of specs
It allows me to detect blocked topics
It allows me to solve complex problem with the whole team
Why do you think the communication with devs is essential to build a product?
They build the vision, making things clear will enable product development
They assess the cost of things allowing us to prioritise for impact
As problem solver, they can great insights on how to solve a user issue
{"name":"Communicate with devs", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"What risk developers are responsible for?, When should you involve devs?, Devs only care about what they should build","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}
