Essay Contents
Goal
This part of the site will host essays and white papers written by ProcessWave Limited to offer insight into the subject of Software Process Engineering on teams large enough to warrant a dedicated Process Engineer. Smaller teams may not have a dedicated process engineer, the task may be left up to the Architect or Project Manager, but ideas here may help them get into this role. Please feel free to send in any useful essay offerings gathered from experience on the battlefield and and we will host them for you.
Why read this?
The general idea is for this site to develop into a definition of the job role that Process Engineers can agree on. The ideas offered here can be implemented practically and be used productively to speed up and promote the better application of process on larger software development teams.
These essays give background and set the stage for why and how software development is in the state it is in. They offer practical solutions to problems and suggest how to go about approaching a process implementation. This is a dynamic experience and once a process has been "implemented", they offer help on how to continue to enhance your process that has already been adopted.
All this is so general software development teams can be more streamlined and the whole development experience can be improved.
Contents (this is all under development and subject to update)
Definition of a Software Process Engineer
Process Scope within an organisation
Background - What are we trying to fix?
The ultimate aim - a Software Factory
War Stories implementing software process
Software Process Requirements - CMM
Qualities of a good Process Engineer
Tip's and Trick's to organise the Process Engineering role by discipline
Work with the Architecture and Analysis & Design
Work with Developers and Implementation
Work with the Configuration and Change management
Work with the Project Managers & Management
Work with the Communication Discipline
Decide if your process will have any other Disciplines