One of the best ways to keep the rest of your team up to speed with what your dev teams are doing is release notes - even if all you're doing is gently reassuring the rest of the organisation that yes, you are patching security vulnerabilities, fixing bugs and quietly making things better.
I love using Slack for this - set up a channel where you post a friendly summary of everything that's being released whenever you deploy to production. Now, here at Skills Matter we're not quite doing continuous deployment yet - we work off short-lived branches that merge to master several times a day, but then once master has passed regression testing on our staging environment, the actual deployment to production is a manual process - we open a master > production pull request in GitHub, merge it, and Heroku does the rest.
We track work in progress using Pivotal Tracker, and we use the various ticket state transitions as:
- Start > a developer has created a branch and begun coding the features
- Finish > the code is done; time for code review
- Deliver > the code has been reviewed, merged to master and deployed to the staging environment
- Accept > the code has been tested on staging; stakeholders know it's ready, and we're good to go live.
Now, this definitely isn't the best branch/merge strategy in the world, but it's the one we've inherited and the one we're using until we've made enough changes to the codebase to be able to deploy PRs directly to review environments.
Select the stories you want in Pivotal Tracker, click the bookmarklet, and it'll copy them to your clipboard as Markdown-formatted bullet points with the story IDs linked to your Pivotal project.
The JS code is here - add a bookmark, paste this whole lot (including the
And here's what it looks like in action: