Agile PPM with GitLab (Nov 11)
Proposal
I want to provide updated information on how to use GitLab features for agile portfolio and project planning at scale. By providing context about what scaling agile means in the beginning, it will help the end user understand the GitLab concepts and how they apply to any scaled agile practices. And hopefully it will also draw attention of users looking for tools for scaled agile frameworks, not just SAFe, but also Disciplined Agile (DA), Spotify, Large Scale Scrum (LeSS), and hybrid models.
The blog post also digs into how to organize/structure GitLab projects and groups for situations where you don't have a single team working on a single source code repository. As this has tripped up some customers in the past, I thought it would be a good idea to include it in the blog.
I've created draft content for review in this google doc.
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title -
Give the issue a due date of a minimum of 2 working days prior -
If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
-
-
If time sensitive -
Add ~"Blog: Priority" label and supplied rationale in description -
Mention @rebecca
to give her a heads up ASAP
-
-
If wide-spread customer impacting or sensitive, mention @nwoods
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
If the post is about one of GitLab's customers, mention @KimLock
and@FionaOKeeffe
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if supporting an event or campaign -
Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)