PaR - Processes as RequirementsIntroduction

PaR - Processes as Requirements


"Did your processes become a heavyweight backpack to be carried by the projects?
And not a lightweight intrinsic approach that really helps the projects?
It gets better when processes are designed as requirements that are reused in the projects.
And this automatically suggests establishing process platforms for product platforms."
           (Ralf Bürger)


>PaRamount<   >PaRade<   >PaRis<


Most accessed


>The Booklet<
Download PDF: PaR - The Booklet

>The Insert<
Download PDF: PaR - The Insert

>The Slide<
Download PDF: PaR - The Slide

>The Page<
Download PDF: PaR - The Page






I now provide the "Code of Conduct" also in German to end the discussions about the interpretation of the English wording. Few further small refinements of the page "About us", e.g. an additional footnote for the CC license, different sort order of the tools, reducing orange highlighting of "PaR".
On the bilingual pages "Impressum / Legal" and "DSGVO / GDPR" I now separate the different languages much clearer and also added the flags.
Minor refinements on the page "FAQ", e.g. on the process types, and reducing orange highlighting of "PaR".
I aggregated some more weeks further down in these News, and for the first time a month (August).



Once again refining the page "About us": adding Ease Solutions, structuring the "Established business areas" (as it is called since yesterday) and thinking further about the trainings. Also, on the page for the "Downloads" I already added the "PaR - for Jira with R4J" in status "in work" (and changed the sort order a bit).
On the page "About me" I refined the technical explanation of the domains and highlighted .info in the first block and .de in the second block. Correspondingly now the others are not domains sharing the same web space, but rather true http redirections, configured on the hosting service provider side.
After a good discussion with Sascha about the "Code of Conduct" I made further refinements, respecting that at the end we all want to earn money with PaR (but NOT PRIMARILY WITHIN the community). And again I reworked the header of the page "About us", and I also further focused the business aspects. Well, it is continuous improvement, isn't it?



Yesterday in the 6-under-PaR Weekly I tested my new miro license with password protected edit access for guests and the video feature within the board. It works fine - therefore, I now added a miro thumbnail with a screenshot to the community web page "About us", and also the link to the miro board that we use (password protected). I now can also make backups of the board and export the board as PDF, so in MS Teams from now on you will find the minutes as PDF. In addition I just created a 4th frame in the miro board for a small "how-to" of miro (already shown in the screenshot also).
We discussed the PaR community "Code of Conduct" (CoC) again and it is up to continuous improvement now. The miro board now only links to the CoC on the community web page "About us".
Also today, I have discussed with Bernhard form Ease Solutions and we want to implement a reference solution of PaR for Jira with R4J. Therefore Bernhard also joins the PaR community and takes that business area.



I registered further domains for PaR (e.g. the short one Now all registered domains are listed on the page "About me", and the page "About us" now only relates to that page. I now also explain some technically background in smaller font.



Thanks to Frank (KoDeCs) for the good and detailed feedback and suggestions on the "Code of Conduct" on the community page "About us" - I changed every sentence and they are now 5 instead of 4 points.



22 x 10 = 2020 --- a good day to see things differently ;-)
And a good day to swap 2 chapters in "The Booklet" (and also in the German edition): "PaRachute" and "PaRameters". The reason is that originally I wanted to get to the tools quickly, because most people want to get into the tools quickly. But in fact the bigger trouble is to convince colleagues, teams or bosses that changing - or at least to try it out - is a good thing. I currently see some people really struggling on this, and I can understand it from my past years coaching big companies. Doesn't sound like a big thing to swap two chapters, that are just two pages in fact (and just left/right in the brochure). But in "The Book" it makes a new structure, because I have much more chapters there, and now I had to split and cluster differently to get the order changed. I am preparing this since days and I have to rework and rewrite a lot, but it feels much better and I think it is worth the work. It is so important to understand the "PaRadigm shift" and to understand what it means to establish it in a company. So, "The Book" now closes with the KPI stuff and the tool features, and I think that's just fine for a book about a methodical approach. I also think that "The Booklet" (English edition) can be published now with ISBN.



Yesterday I talked to some experts who want to join the PaR community, also one from a large automotive OEM and a consultant. I think it is time to set up a "Code of Conduct" to ensure that potential customers joining the community don't get overrun by the freelancers and consultants. Therefore, I have set up a draft, discussed it with some core members and added it to the page "About us" and to the Miro Meeting Board. So, it is now open for continuous improvement.
I had good discussions about process platforms aligned with product platforms, especially system architectures and feature trees.



I was asked to help applying PaR for a business process of an organizational unit of a German government agency. I was surprised about the modernity of that organizational unit, but I had to explain why I'm always talking about development processes for complex projects and what that finally means. However, I have added that question to the FAQ page of this website.



Several good discussions ongoing after the presentation of PaR at the re:WORK conference in Berlin. Some people and companies are also actively working on in. Meanwhile I continue working on the difficult chapters 4.x. Looking forward to the next community meeting tomorrow.



Yesterday and the day before I started to split the chapter 4.3 of "The Book" and described Product Family Engineering with a nice diagram. Then I reviewed the chapter 4.2 (Cascading) again; well, I reworked it again, and I also refined the new diagram, spending another full day on a single page :-( It is quite difficult to describe it in a way that the reader instantly understands it and thinks it is simple - like always: when it is easy to use, it was difficult to make it.


CW 41

I reworked in "The Book" chapter 4.2 (Cascading "what" and "how") in text and also the diagram, to show cascades instead of a 2x2 matrix. This shows the basic natural structure much clearer. Also some sentences are much more focused now.
Also, in "The Book" I refined the introduction chapter "PaRamount". Correspondingly I renamed the pages of the website "Abstract" to "PaRamount" (with a hint to the introduction chapter of "The Book"), "Challenges" to "PaRade" and "Overview" to "PaRis". The "PaRamount" chapter and web page are in sync again and mention the holistic component model in the last sentence. This topic is already reserved for chapter 4.3 (Process platform for product platforms) that will maybe be broken down into 3 chapters for product platform, process platform and the different stages of possible combinations.
In the English and German "The Booklet" I moved the reference to the book-chapter about process families with process platforms from page 12 bottom to page 8 benefit 5, enhanced by "and even the integration of domain processes into components, also for agile approaches". With this small enhancement I carefully try to motivate a true component model approach, which indeed is still somehow over the top for most companies in our days. It will also take me a cold winter to fully explain it in "The Book" and to start sophisticated discussions about it. The 3rd paragraph on page 12 is correspondingly almost completely reworded to further explain this from the tool side, also motivating PaR against graphical process design tools. Therefore, this paragraph now also contains more arguments against trying to work in a graphical process within a complex individual project.
For the German "The Booklet" ("Das Heft") I now also translated the diagram elements on the front cover to German (and also the SSE ;-)
I had a first PTC session with Sascha where we setup a document, added some VDA ASPICE regulatory requirements, made a first relation and snapped a screenshot for the title page and for some explanations within the "PaR - for PTC".
Now also the English video and slides of the PaR introduction at the re:WORK conference are online. See page "The Videos".
Both presentations are available as PPTX for the community in MS Teams.
I updated "The Deck" with some of the translated slides, and I separated the German slides of "The Deck" into a separate german deck. The PPTX of both decks are available in MS Teams of the community now.
Several attendees of the re:WORK conference requested "The Book" as Draft PDF - and they got it instantly of course. From discussions with them I also enhanced the new FAQ page.
Page headers have been improved (description and h1) to improve Google search.
I further improved the pages "About me" and "About us" (I extended the introduction, I added the asset list and I added me ;-)
Also I added a new page "FAQ", as suggested yesterday in the community weekly.
I refined the menu a bit: I removed the 3 white lines for "Processes / as / Requirements" underneath the diagram to gain some space for the new menu entries. I reworded the section "PaR" to "PaR Excellence" and the section "Community" to "PaR Community".
I separated the contact page into two pages, one for "me" (further reduced, focused on being the main contact for PaR and being the responsible for the online web domains) and one for "us" (the community).


CW 40

Working on business requests, conference discussions and further method refinements. The todo list got longer and I will work it off next week (e.g. a FAQ page on the website). Then I think it is time for publishing The Booklet with ISBN officially. Also, I prepared the Miro board for the next community weekly tomorrow. Due to the success of the re:WORK conference we plan further conference speeches. We got many new contacts for PaR and always a very positive feedback. The pre-recorded video and the slides as PDF are now >online<.
I also posted the 5th splash on XING.


CW 38

The backup-video for the re:WORK is done, 30 minutes, recorded with Logitech Capture on Logitech StreamCam camera, slides as MS PowerPoint and PDF, cut with Apple iMovie, uploaded in Youtube as 1080p HD, added to a new navigation section - will be available next week after the conference.
Sascha and me had an interesting discussion with IBM about their implementation of ASPICE and typical automotive process in upcoming versions of DOORS - pretty close to PaR. We agreed on continuing the discussion.
Good feedback from review of the slides from Sylwia and Frank.
I also posted the 3rd splash on XING.
Thanks to Martin from IESE Fraunhofer I can present the PaR approach at the >re:WORK 2020 conference< in Berlin 27.Sep-29.Sep.
During translation of "The Booklet" to German I also changed some wordings in the English version. I also updated the headlines of the needed tool features, to name a bit more the features themselves and not their purpose. I updated this also in "The Book", "for Jama" and the tool template "for Any" (who the f...k is Any? :-))
No, I don't have an online shop and it is no problem for the GDPR; therefore I renamed the page to "How to buy". There I now describe how the PDF for "The Book" can be requested, and yes, I added this information - and how I handle the data - also to the GDPR. I also updated the page for "Downloads" accordingly (and they are still free without any registration or shop).


CW 37

The German translation of "The Booklet" is done and available for free download now.
The new "WOP" item type is now briefly explained in "The Booklet", being mentioned as "work-products" 3 times. In "The Book" it is explained with more sentences.
Since we are now starting to create the "PaR - for Polarion", "PaR - for PTC" and "PaR - for DOORS" also, I first created a template from the "PaR - for Jama" and then copied and adapted it to become those drafts. I already show on the "Download" page that we have these documents in work now.
The tool implementation exemplifications now are for free download without request also. Therefore I removed the "PaR - for Jama" from the "How to buy" page.
Only "The Book" and "The Booklet" will also be for sale as high quality prints in book stores, on epubli and on Amazon.
The general sort order now is: "The Book", "The Booklet", "The Insert", "The Slide", "The Deck", "The Page", "for Tool", "The Mug".
I got the newest version of "The Mug" and I really like it!
Added a 2nd board to the PaR Community Miro: an agile task board.
Good to hear that community members are working on a requirements set for Automotive Cybersecurity and on a Polarion tool implementation.
1 month online and we just had our 1st PaR Community Weekly, a channel called "6-under-PaR" in Microsoft Teams, currently equipped with Posts, Files (PaR sources and meeting minutes), Wiki (with a first FAQ entry) and a Miro board. We're starting small with 5 people out of 10 online, but we're thinking big with good topics.


CW 36

Now I reuse the different diagram versions as PDF instead of redrawing them everywhere. Further reworking and refining the PaRis detailed map: applying colored frames in different dashed styles, combined with gray frames in the background, testing the accessibility with color-blind persons, also testing print and black/white, adding the WOP (work products) for in- and output of process activities becoming project actions, changing the descriptions on the COP (explanations instead of examples), using lower case characters for the descriptions, preparing multiple versions in PowerPoint for pasting as PDF in the other documents.
Good discussions about applying PaR in an agile context with multiple teams and about applying PaR for an industry leader with heavy certification load.
I replaced the font for the blue and orange filled circles with "Hiragino Sans" in width "W9" everywhere to enhance readability, mainly for printing.
I have set up the Microsoft Teams PaR team and invited for the Community Weekly "6-under-PaR" (getting it done on Monday for a 7-day-week ;-) with a corresponding Microsoft Teams channel, including the Miro app also.
I spent a lot of time with setting up my new RØDE microphone, Logitech StreamCam, Logitech Capture app and the studio Soft Light (with more than 100 LEDs) - see fotos on page "Contact".
Also, I worked hard on the Jama ReqIF export with round trip updates - very tricky!
"The Deck" is new - currently containing 18 PDF slides that can be used in presentations. Therefore, I reorganized the download page, now having a "Core" and a "Helper" section.
"The Insert" is new - download, print, fold, insert into multipage documents, for overview to ease reading and as book mark.



All Splashes are now done on LinkedIn and also presented on the Webpage "The Splashes".
New page "Articles" (see navigation tree left) with the first article about PaR on LinkedIn.
First time I sent a newsletter to the community, since we are more than 10 now.
Updated my XING profile to prepare the publishing of "The Splashes" also there, as on LinkedIn before.
The GDPR (DSGVO) is updated regarding 1&1 IONOS hosting and WebAnalytics, SSL certification, CloudFlare CDN (Content Delivery Network) usage and document distribution license. Website copyright remark (see navigation menu on the left) extended by CC license (linked to legal/impressum).
Website and content now provided unter >CC BY-SA 4.0< (see also >summary<), as described in my >legal< descriptions (German: Impressum) as well as on page 1 of each multipage PDF offered for download or sale.
In "The Booklet" the Needs got orange numbers now, like in "The Book". These are now referenced in the PaRis explanation, like the benefits. This is now also explained in the first chapter of the PaRis explanation. But I will still leave the level of PaR approach requirements for "The Book" only.
Today I simplified the covers by removing the explanatory texts from the diagrams.
I numbered the benefits now on page 2 (the small "The Page") and I now explain these benefits - and thereby the complete PaR in a nutshell - in the chapter "PaRis detailed".
Impressum in "The Booklet" and "The Book" reworked completely to prepare publishing with ISBN, thanks to the author support of epubli.
Used the SWOT to rework "The Slide" and "The Page" for the challenges and solutions as well as the benefits.
Impressum/Legal and DSGVO/GFPR adapted for the PaR web space.
The PaRis diagrams now show the "Project" in the middle, partly behind the "Corporate Process Requirements", because the projects reuses these ones. To help each project is our focus, therefore it should be in the focus of the diagrams also. The hand-painted diagrams now also say "Project" instead of "Development", because not everyone understood that this meant to be the project.
The new website of the new domains https://ProcessesAsRequirements.* is now (07.Aug.2020) online. The page of Ralf Bürger (SSE) has been reduced to a PaR tidbit accordingly. These new domains with this new website shall be the home for PaR. This News-section will cover the progress of the website and PaR itself.