-
Notifications
You must be signed in to change notification settings - Fork 438
Planning
Establish a clear structure for milestones to guide the allocation of teams and epics.
Organizing different teams around milestones enhances predictability in results, budgeting, and staffing requirements.
- Each milestone represents a significant phase in the project, encompassing one or more epics.
- Milestones provide a framework for estimating the scope and duration of epics, thus offering a sense of completion and progress.
- We will have milestones for OSS, Infra, Design partnerships, Tech Partnerships, Management - different teams are on each, but some people are in more than one.
Align teams with specific milestones to streamline project execution.
Every team is assigned to work towards achieving a designated milestone.
- Teams are responsible for completing the epics and stories assigned to their milestone.
- Regular updates and the return on the status channel are essential for monitoring and adjustments.
- Milestone: A significant project phase with strategic goals.
- Epic: A key deliverable within a milestone, containing several stories.
- Story: A specific feature or function detailed within an epic.
- Task: Actionable steps required to complete a story.
- Each epic should be clearly defined with its set of stories and tasks to provide detailed guidance for teams.
- Estimations for completing epics will contribute to overall project predictability.
Bugs and social posts do not require an epic due to their timeless nature.
Estimate man-hours needed weekly for bugs and social posts, allowing for flexible allocation without detailed scheduling.
Reallocation of teams (e.g., partnerships to the OSS and infra team) mid-epic may be necessary.
Communicate the need for reallocation well before the weekly planning session to Fernando, Duncan, and Timo.
Ensures that estimates are accurately adjusted and resources are effectively allocated.
Adjustments to team allocations and epic assignments should be made based on strategic priorities and resource availability.
Every task and epic must have the proper labels and a description for clarity and organization.
- Title categorization: The category of the task or epic must be enclosed in brackets [Category] before the name of the title.
- If we have a category for example: [Intel], if we are working with just one objective on Intel, it should be in the same epic, and the tasks to close this epic, like, a POC is a stories with tasks; Meeting and alignment is a task inside it and so on...
- The tasks and stories within epics will adopt the same category brackets to maintain consistency and ease of identification.