Section 5: project interface in GitHub confusing

[anenadic]

From AZ pilot 2: Project interface with GitHub confusing. Wanted to have two kanban0-style boards, one for to-do/progress/done, another for must-have/would/could/wont. But couldn't have that. Circumvented by using custom labels to issues (for moscow prioritisations)
How do you assign effort estimates to issues?
Can add effort estimates to issue titles as an option
Milestones for timebox

[anenadic]

This part of an issue:

How do you assign effort estimates to issues?
Can add effort estimates to issue titles as an option

was addressed in 51dedd2.

[steve-crouch]

Discussion with @anenadic - a basic first-pass edit could be:

• Can use milestones for capturing issues within basic timeboxes, can use projects for more fine-grained management
• Clarify project interface at account not repository level
• Can associate repository with a project in GitHub

[steve-crouch]

Discussion with @anenadic - a larger editorial pass could be:

• Software issue management in a team
  • Individually make an issue
  • Learn about notifications and mentions to communicate within team about issues
  • Choose a repository, and do team exercise
• Product management using agile techniques
  • Estimation
  • Prioritisation [using milestones]
  • Sprint exercise
• Project management
  • Greater control with project boards
  • Managing multiple related products [with another repository]
    • [Mention project boards to manage multiple projects individually as well as a team]
    • [Example: like SSI work with multiple repos, could organise via a Project; and this applies to individuals working on multiple repos]