Source

source: https://www.youtube.com/watch?v=vHUEOYbH8Mo

where I heard about it: stuart posted to triumvirate

Notes

starting point

projects can take issues from many repos, issues can live in many projects

Main Questions when designing a project: what does this project need?

who is looking at it?
what are the questions they have?
- each question that may be asked can be a custom view (or be satisfied with a custom field)

Structure

Opportunities Backlog
- When a pitch is accepted, it goes into the next:
Program Overview
- answers: what is in progress, what is at risk, who can i ask questions, what’s happening next?
- handed off to feature team next. each of those items has its own project board:
Feature Overview
- focused on a discrete feature deliverables
- contains all tasks necessary to ship
- answers: what are the broad sets of work comprising this feature, what is assigned to me, what is the task sequence, what can i work on now, is it equally spread across team?
Other Backlogs

Building a feature overview

https://youtu.be/vHUEOYbH8Mo?t=912

create new project (maybe from template)
name it with feature name
write out the things that make up this feature - basically as engineering tasks; draft issues
maybe add a new field for “area of work”, then add these to the tasks
consider using week segment iterations

Converting to issue

This turns the task into an issue. Use the Task List to manage the separate things to be done in this. These will start as drafts, but can then be converted to issues. You then need to bulk add them to the table view

Can create a branch from an issue

View filters

asignee: @me, iteration: @current - would update for who is looking at it and when it is now.