This repository was archived by the owner on Jun 10, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Product development process
Tobias Schubotz edited this page Apr 24, 2020
·
3 revisions
- Software engineers 🛠️
- Product managers 🚀
- UX/UI designers, UX researchers 🎯
- QA engineers (?)
We are doing sprints with a length of 2 weeks (10 working days).
| Week | Day | Activities Sprint A | Activities Sprint B | Activities Sprint C | ... |
|---|---|---|---|---|---|
| 1️⃣ | Monday | ||||
| Tuesday | (Estimation ⚖️), Sprint planning 📑 | ||||
| Wednesday | |||||
| Thursday | |||||
| Friday | |||||
| 2️⃣ | Monday | Work on requirements ✒️ | |||
| Tuesday | Work on reqs ✒️ | ||||
| Wednesday | Work on reqs ✒️ | ||||
| Thursday | Reqs final at 3pm ✒️ | ||||
| Friday | QA 🚨 | ||||
| 3️⃣ | Monday | Release 🚢 | |||
| Tuesday | Sprint review 🚦, retro 🎢 | (Estimation ⚖️), Sprint planning 📑 | |||
| Wednesday | |||||
| Thursday | |||||
| Friday | |||||
| 4️⃣ | Monday | Work on requirements ✒️ | |||
| Tuesday | Work on reqs ✒️ | ||||
| Wednesday | Work on reqs ✒️ | ||||
| Thursday | Reqs final at 3pm ✒️ | ||||
| Friday | QA 🚨 | ||||
| 5️⃣ | Monday | Release 🚢 | |||
| Tuesday | Sprint review 🚦, retro 🎢 | (Estimation ⚖️), Sprint planning 📑 |
Meeting outside of sprint cycle: Gnosis Safe Team weekly every Tuesday.
- Product managers 🚀 define requirements
- Product manager prioritizes tickets
- Always make sure that tickets are prioritized properly.
- Software engineers 🛠️ add technical details and split epics up into tech tasks
- UX researchers perform research and tests
- UX/UI designers 🎯 refine screens
- Prototypes on Invision
- Later stages on Zeplin
- Software engineers 🛠️ discuss technical details
- The entire team 🎳 thrives for clarifying open questions and thriving for adding details to requirements
- The requirements should be final from product the week before a start of a sprint at Thursday 3pm.
- Estimate implementation effort for features
- Run by Software engineers 🛠️
- Doesn't have to happen Tuesday as indicated in the table above. This is just the last possible moment.
- Team 🎳 commits to a set of features
- Potentially reprioritize tickets based on estimations
- Ideally no technical discussions
- The specific QA process is to be defined.
- Types of QA that make sense:
- Feature QA
- Release QA
- Regression tests
- Requires release notes and potentially updated store assets
- Mobile apps are release to the store
- Further activities to be defined, e.g.
- Internal announcement on Slack
- External accouncement on Twitter
- Meeting for the entire team 🎳
- Review features and completion.
- Demo current state and new features.
- Meeting for the entire team 🎳
- Reflect on performance and collaboration during the last 2 weeks
- Decide on process changes.
- Specific retro format to be defined
- Team meeting with the entire Gnosis Safe team 🎳
- Independent of the sprint activities