Every team needs an agile process. Or two.
Maybe some teams can get by without strictly following documented processes every day, but when it comes to agile software development teams, it’s simply not an option to operate in the dark.
Since software is complex and easy to mess up, processes mean the difference between a great product and a crappy one. Without processes, software teams will spend more time squashing bugs and dealing with support headaches than they will actually developing the product…
The exact reason we created Process Street is to help businesses avoid that nightmarish cycle, and, of course, we use Process Street ourselves to help run the agile processes behind the scenes.
We use regular agile processes like:
- Daily standup meeting
- Sprint planning
- Sprint turnover
- Sprint retrospective
We also run routine QA processes like:
- GitHub pull request procedure
- Weekly WordPress maintenance
- SSL certificate renewal
And, finally, we have a set of training processes:
- Developer onboarding
- How to set up your development environment
- Pull request review failed procedure
- Pull request merge procedure
These are all regular tasks for the team, and the reason they were created was because we found they have a high margin for error.
Scroll down to find the exact processes we use.
If you want to tighten up the way your software team works, hit your sprint targets, and efficiently train new development hires, then this post will show you how. We even reveal the exact processes we use and a workflow diagram detailing the journey an issue takes from start to end.
Continue Reading