In a previous post I talked about a Lightweight Ticket Process, but glossed over how we actually identify the steps we need in our process.
It's important to note that I am talking about the process we apply to single set of changes, not the high level process we might apply to a complete project. I have referred to this in the past as a "Ticket Process", other people have used the term change set. However it can be any sort of change or piece of work.
Remember the objective of the Lightweight Ticket Process is to have a process that is as simple as possible, but no simpler. Some of the issues to investigate:
Make sure that you cast around for the following sources of information
- What is the desired final outcome, purpose or product from the process. e.g.
- The creation of a review document notes
- The fixing of a bug in the current development
- The generation of revenue by implementing a custom feature
- Asking a question
- Where in the Application lifecyle was it initiated and by whom e.g.
- Project Initiation
- Production support
- User Acceptance testing
- What pieces of work need to happen to create the desired outcome? e.g.
- Code changes
- Rebuild of software
- Change in specification
- Change in budget or other piece of project documentation
- Deployment onto a production environment
- An update to a build system configuration
- What role is responsible for performing the work. e.g. developer, project manager...
- What reviews and approvals need to occur before and after the work is complete, e.g.
- Review of cost, benefit, impact and risk
- Approval by Change Control Board
- Code review
- Sign off by Quality Assurance team
- What roles are responsible for performing reviews or authorisation.
- Any process requirements from the customer or other external entity e.g. the FDA
Now comes the hard bit.
You have followed the activities above and come with a beautiful complete process. Unfortunately it is far too complex. So now we simplify, which can be difficult to do.
- This projects current processes, documented and undocumented
- Organisational processes and standards
- Similar projects in the same organisation
- External standards such as ITIL
It is better to start with too simple a process and improve it as the team understands more, than to start with something hard to use. Unfortunately it is very easy to give a team the the latter as the siren call of "complete process" is highly seductive.
- Cut out "information" steps and roles
- Determine which of the outputs from each process step are useful. What are they used for? Nothing obvious? Then cut it out
- Be brutal and cut out any thing that not essential and be severe with your definition of "essential"