PaR - Processes as RequirementsPaRade
 
 

PaRade of challenges and solutions

 
 

Nowadays we perform projects or even organize companies in an agile fashion to stay focused, to inspect and adapt often, and to enable teams to do the right things. We see innovations spreading faster, new products emerging in many variants, and windows of opportunities closing quicker than ever. On the other hand the processes to be applied in the projects often get more and more heavy-weight and frozen, like being defined once and forever.

In all complex organizations that engineer complicated products, but also in many industries and special domains we see projects struggling with the regulatory standards and the corporate processes that are to be applied. During my coaching of complex projects in recent years I discovered 5 challenges. They all can be addressed by changing the way to deal with bulky standards and processes. Bringing these deeply into the projects makes them feel more intrinsic and natural. I derived dedicated needs from those challenges and went further down to requirements to figure out a systematic methodology, finally based on the PaRis (PaR information system). Together with KoDeCs I successfully applied a similar and more basic approach during the past years at an automotive supplier and this was driving me to work it out more systematically.

I created the PaR approach to address these challenges. While most companies and tool vendors try to set up the requirements according to the regulatory standards and corporate processes I bring those standards and processes also into the requirements tool, because they are nothing else than requirements. When the requirements engineering tool is also used for managing change requests and reviews and testing (validation and verification) and maybe also risk management, then it becomes an even more holistic approach.

 
 
?
 
How do you design corporate development processes that are flexible enough to be a help for all kinds of your projects?
 
 
 ! 
 
Define the processes as requirements in dedicated sets that can be reused as needed in the projects applying the teams' standard RE tool!
 
   
 
 ? 
 
How do you unite all needed regulatory standards with the corporate development processes to make it a holistic approach?
 
 
 ! 
 
Define the regulatory standards also as requirements and relate them to the corporate development processes with bi-directional traceability!
 
   
 
 ? 
 
How do you establish sustainable corporate development processes that can learn together with or from the project teams?
 
 
 ! 
 
Merge the process requirements with the product requirements in the projects and improve both platforms by synchronizing requirements!
 
   
 
 ? 
 
How do you ensure that your projects continuously comply with corporate development processes and regulatory standards?
 
 
 ! 
 
When the standards and/or processes are pulled as requirements into the projects, the RE tool can monitor the bi-directional traceability!
 
   
 
 ? 
 
How do you monitor the actual progress of the project and product maturity, in addition to monitoring time and budget?
 
 
 ! 
 
Defining a status for process requirements, adding templates for simple documents, and real reviews will help measuring progress in maturity!