[BD-038] How we work
Sprint Length
Our sprints are two weeks in length.
Meetings
What | When | Participants |
---|---|---|
Sprint Planning Meeting | Monday [Start of the new sprint] 1 Hour? | OpenCraft, TNL-PAK, Product, Manager, UX |
Standup Meeting | Tuesday, Thrusday | OpenCraft, TNL-PAK |
Sprint Review | Friday [End of sprint] 30 - 45 mints 9PM PKT - 945PM PKT | OpenCraft, TNL-PAK, Product, Manager, UX |
Sprint Planning Meeting
Prerequisites: Product Backlog ready for review @ProductOwner. This means adding acceptance criteria, requirements, and necessary details for the team to accurately estimate the level of effort.
Actions: Review the prioritized Product Backlog
Output: A sprint backlog [sprint goal]
Removes Need:
[WED 45min meet] Kshitij Sobti and [BD-38] Discussions: Improvements & Integrations
[Mon 30 mint meet] TNL-PAK planning
Standup Meeting
Prerequisites: None
Actions: Discuss daily goals/work & Identify blockers.
Output: Meeting Notes/Logs
Removes Need:
[Tuesday, Thrusday 30 mint meet] TNL-PAK Standup in the favour of Meeting Notes/Logs
Sprint Review Meeting
Prerequisites: Prepare Demo/Showcase work done
Actions: 1. Demo the work. 2. Discuss if the sprint goal was achieved? 3. Next Agenda - Whats' coming up. 4. QA session
Output: Demo and Sprint Status Updates