Development process content feels in need of a refresh

[46bit]

https://team-manual.cloud.service.gov.uk/team/working_practices/ starts by showing our Development Process, but it's hard to make changes to this content and it isn't very in-line with the Doing--Reviewing--Approving model that Rubbernecker/PivotalTracker create.

[bleach]

I looked back on #26 and there wasn't enough clarifying context. So here's some:

This is explicitly supposed to describe the doing-reviewing-approving process. It looks like some of the text within the diagrams describing which roles do what is outdated.

This came about because we were asked by the Information Assurance team for some documentation on development process showing how changes got into production. I thought this would be useful to have written down and I didn't want to bury this in an IA document that the team don't refer to very often, so I put it here and added a link from the IA document.

At the time there wasn't anything that I could get to work with mkdocs that would produce diagrams from source, so we ended up with the need to install blockdiag and run make. There are middleman extensions for diagrams that could be tried.

[46bit]

Thanks @bleach! The diagrams and description are quite effective from an IA point of view, but I've found less so from other contexts (e.g., a new team member trying to understand what they should do.)

I'm moving off of the PaaS tomorrow 😢 and these issues are something of a dump of ideas in my head.

[alext]

@46bit Do you think #230 has addressed these comments, or does it still need further updating?

[46bit]

We've addressed this well.