PaR - Processes as Requirements

methodical framework

  
  next Monthly: Su 15^th Mar 2026 at 4^pm >UTC⁺¹<
  topic: Future of Processes
  >add to calendar<   >Zoom<   >About us<

  done:

Did your processes become a heavyweight project backpack?
And not a lightweight intrinsic helping approach?

It gets better when processes are designed as requirements.
These requirements can be reused and improved by the projects.
They also can be linked to regulatory standards as requirements.
And to product requirements as platforms in product families.

>PaRamount< - simple explanation (from the introduction chapter of The Book)
>PaRade< - 5 challenges with 5 keywords and 5 potential PaR solutions
>PaRis< - PaR information system (graphical overview of the words)

Join the PaR Community for free to learn more and have fun.
Check the page >About us< for more information and see what we do when we >gather<.

Favorite downloadables:

News and Updates

• At the Mar-Monthly let's discuss about the future of processes - if there is any at all.

• Happy New Year 2026. Personally I'm looking forward to the new edition of The Book (one day). Stay tuned.
• The Jan-Monthly might focus on the recap of the ESE congress again, because next day we have a recap meeting with the attendees.
• By the way: I recently updated the page About me with a new profile photo and my new PaR-car ;-)

• Let's recap the ESE congress where Martin (Fraunhofer IESE) and I (Ralf SSE PaR) hold a workshop of 6hrs about reuse from platforms.
• We intensively showed PaR also as an example for process platforms.

• Sorry, I have to skip the Oct-Monthly due to some very important customer workshop. In the Nov-Monthly let's talk about really simple process design that really works. That's all you need, you just have to do it.
• In the Oct-Monthly let's talk about really simple process design that really works. That's all you need, you just have to do it.

• Sorry for the problem with the .ics calendar file of the monthly this time. I'm happy that the direct dial-in worked anyway.

• Let's talk about Test-Cases, Test-Runs, Test-Plans with PaR. I can show an example, implemented with easeRequirements, a famous requirements plug-in tool for Jira.

• Sadly for the very first time in years I have to drop a community sessions.
• I will attend a 2-day workshop 14/15.Jul at a huge customer for applying new efficient processes to the platform teams.
• This work is planned until end of year but I will join onsite only on Wed/Thu each week.

• At the community monthly 15^th May as well as June I can give an overview of team collaboration with PaR.
• With PaR it's ideal having teams for standards, processes, projects and platforms, working closely together by bidirectional traceability of the requirements.
• This topic is also planned to be presented at the ESE conference in December 2025. It is a dedicated chapter in The Book also.

• For the community monthly 15^th Apr let's discuss how to create a compliant process design efficiently.
• Yes, I repeat that topic from March, because the 15^th was a Saturday then and nobody wanted to waste the weekend for PaR ;-)
• Watch out, we switched to summer time on the last weekend of March (as usual), so it is CEST now instead of CET, i.e. now UTC+2 instead of UTC+1.

• I got an invitation to speak at the next ESE congress in Sindelfingen from 1^st to 4^th Dec 2025.
• For the community monthly 15^th Mar let's discuss how to create a compliant process design efficiently.

• For the community monthly 15^th Feb let's further discuss how process requirements with roles and input/output work-products can be defined.
• I presented this approach also at the inhouse easeSolutions congress live in Munich on 13^th Feb, so the presentation is fresh in the mind ;-)
• Further more, I will describe this approach in The Book in the chapter for process design, together with a diagram showing the relations.

• For the community monthly 15^th Jan in the new year I plan to show how process requirements with roles and input/output work-products can be defined.
• 2024 is over now, so I transferred 2023 to the History page.

• >History<