How we ship new features · Resend

At the top of each list, there is a HIGH LEVEL card that explains exactly what is going to happen with that release, written in the format of a Jobs To Be Done statement. The HIGH LEVEL card also contains a link to the Sketch file that has all of the designs for that release.

the engineers are also helping daily on discovery (and many of the best innovations come from that participation, so this is not a minor point), and the product manager and designer are also helping daily on delivery (mainly to clarify intended behavior). But this is what's going on at a high level.

The first was a list of questions, assumptions, and risks. As team members learned, they moved through this list, answering questions, paying down risk, and adding new questions. The second list was a list of possible features. These were features that the team and stakeholders thought they might need but for which they had no evidence of actual ne

Engineering. Once the repeatability of the project effort is secured, the software project can, for the first time, turn its attention to the enticing aspects of software engineering.