How we do agile/sprints remotely - 2021-03-02
Proposal
Part of our engineering + remote work series/collection, how we do agile and sprints remotely. Will add any relevant videos to the issue in description/comments.
Questions for respondents
- How does GitLab (the platform) enable teams to work more agilely? (Here is a blog post we published on the topic, but I'd like to know your perspective as well)
- How does your team specifically use sprints at GitLab?
- Do you have experience working with Agile for software development while working in an office setting, at a previous company?
- Do you feel that GitLab's structure as an all-remote async company makes it easier for programmers to work agilely? Why or why not?
- Thinking specifically about Agile/sprints, what are some of the benefits of working in an office setting, with your colleagues next to you? What are some of the challenges?
- Are there any major differences between conducting a sprint/Agile software development on an in-person team vs. an all-remote, asynchronous team?
- What are some tools, strategies that are most useful for remote, Agile software development? Any links/resources I should include in this post?
- What advice do you have for engineers that are adopting Agile for the first time, or are working remotely for the first time?
- What else do I need to know but haven't asked?
Some relevant links:
- https://about.gitlab.com/blog/2020/11/11/gitlab-for-agile-portfolio-planning-project-management/
- https://about.gitlab.com/blog/2018/03/05/gitlab-for-agile-software-development/
- "A Day in the Life of an Agilist"
- Keynote from Virtual Commit: https://www.youtube.com/watch?v=t8BvRMalbkM&list=PLFGfElNsQthYQaTiUPQcu4O0O20WHZksz&index=10
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title and apply the appropriate milestone (e.g. Blogs October 2020) -
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 @rebeccato give her a heads up ASAP
-
-
If wide-spread customer impacting or sensitive, mention @nwoodsto 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 @KimLockand@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)
Edited by Sara Kassabian