Improve Project Boards Standard

[coreyshuman]

The standard for project boards needs some major improvements. It assumes a lot of previous knowledge and is very light in details. The following tasks would majorly improve the effectiveness of this standard:

• Provide context for the terms. What is an SOW? What is a feature set? etc...
• Provide context for the goals this standard tries to achieve. (sow tracking, PM reporting, etc)
• Include screenshots of an example SOW and matching project board(s). See QA standard for good usage of screenshots.
• Provide more detail on HOW to setup the project board.
• Fix error: SOW is Scope of Work, not Statement of Work

[Karvel]

I would further explain the difference in flow between Fixed Bid projects (where the SOW defines the project boards and milestones are easier to predict months in advance), and Time and Materials projects (where projects and milestones are usually defined through sprints).

[ryekerjh]

@Karvel @pratimasakinala Would you be willing to collab on this with me so that we can actually get it updated IRL?

[ryekerjh]

@Karvel @pratimasakinala ping ^^^

[kmausolf]

@ryekerjh If you need assistance with this, let me know! I have a bit of experience setting up these boards and translating SOW to issues/project boards.

[Karvel]

@Karvel @pratimasakinala Would you be willing to collab on this with me so that we can actually get it updated IRL?

Sorry, this came in when I was out of the office and I didn't see it. Let's do it!

[michaelachrisco]

With @coreyshuman most recent talk, I believe we should add in those details into the S&P repo. @kmausolf and/or @Karvel I would love to discuss and get this in writing so the rest of the shop can start having more standard Github boards.