Every good project starts with a brief. Before you build a feature or ship a product, it’s important to make sure everyone understands why you’re doing the project. The project brief acts as an anchor for the team and defines the problem, proposed solution, audience, metrics, and risks of the project.
However, once the project starts and specific tasks are assigned in Jira, the brief can quickly be forgotten. If the brief is written in one tool while progress is tracked in another, teams can lose sight of their original goals and scope creep can quickly set in.
This Coda doc gives project managers a superpower: a
Feeling stuck? The Coda team can help! Chat with an expert by clicking the question mark icon in the bottom right of the screen.
Status in Jira
Initiative Custom Label Field
JTP-51 Add one-click checkout option to shopping cart (Done)
JTP-50 Shake Android app to share (In Progress)
JTP-49 Add PayPal as a payment option (Backlog)
JTP-48 Conduct 30 customer interviews (Selected for Development)
Selected for Development
JTP-47 SEO optimization (Backlog)
JTP-46 Migrate from Azure to Snowflake (Done)
JTP-45 Add 1Password support (In Progress)
JTP-44 Add “fun fact of the day” to login (In Progress)
There are no rows in this table
A few of the 25,000+ teams that 🏃♀️ on Coda.
Coda is an all-in-one doc for your team’s unique processes — the rituals that help you succeed. Teams that use Coda get rid of hundreds of documents, spreadsheets, and even bespoke apps, to work quickly and clearly in one place. This template is a Coda doc. Click around to explore.