Continuous Collaboration: Breaking down barriers in Software projects
summary
Argues that Continuous Delivery plus enforced collaboration still left bottlenecks, so the team builds Probo.ci creates per-pull-request Docker review apps that integrate with GitHub/Bitbucket, Jira, Slack, Zendesk and visual regression (Backtrac), run Behat and PHP CodeSniffer, pin builds and preserve test content, and migrate from RethinkDB toward Postgres. Shows how per-PR environments tame workflows with dozens to ~100 open PRs, reduces lead-developer bottlenecks, and shifts work from timed sprints to moved from sprint releases to Kanban continuous releases for faster, reviewable launches.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:59First, a little history
- 6:57Lead developer assigns tickets
- 7:12Devs are happy to help
- 7:24Project Manager checks in
- 7:41PM asks Lead for a review
- 7:58Lead checks out the branch
- 8:16Devs hear the grumbling
- 8:44Dev regrets the mistake
- 8:56Lead merges the fix
- 9:15The client wants to deploy only one feature they need and are happy with
- 10:10Client is not happy
- 12:55Lead assigns tickets
- 13:06Project Manager checks it
- 13:30Client sees that it is right
- 13:40Projects run smoothly
- 13:50And the client is happy
- 16:33Continuous Collaboration
- 20:09CC changes how we work
- 21:21Github & Bitbucket Integration
- 21:44Open Source
- 22:16Sleep Peacefully with Probo!
