I changed the comments on the diagrams for REG and COP to make it more consistent:
The detailed PaRis now has the specific "laws, norms, organizations, customers"
("laws" instead of "legal") and the overview PaRis now has corresponding
German automotive examples "StVO, ISO, VDA, VW" instead of "ISO, IATF, ASPICE,
Similar in the German translations.
I took the opportunity to change all arrows of the overview PaRis diagrams to 3px thickness
and large style arrow ends.
Also I changed the line distance to 0.8 consistently.
These changes also affected the cover pages, but I did not update all thumbnails for that ;-)
The titles are now updated, i.e. The Book, The Booklet, The Insert, Das Heft, and The Deck in English
and German got the addition "methodical framework".
The thumbnail images of all documents are updated everywhere, on the website as well as in the
In all documents the short versions of the 5 challenges now have the key word upfront, also in
an italic shape, e.g. in The Page, The Slide and The Deck.
They are also highlighted in the table of contents of The Book, The Booklet and Das Heft.
The Splashes are now sorted on the web page, in The Booklet, in Das Heft, in The Insert and in
The Deck (English and German) by content and not historically any more.
The first Splash (Intro) now got the 5 key words also.
The last Splash is now everywhere the updated SWOT (see below).
The order of the chapters in The Booklet and Das Heft is changed again to have the tool features
early again, the KPIs afterwards (because they use some of the tool features) and then the
PaRachute and the PaRadigm Shift, because the PaRachute now is a sub-chapter of the PaRadigm Shift
in The Book also (although there it comes before the tools and KPIs).
The source files and the updated PDF of The Book are again available for the Community in the
MS Teams channel in the tab "Files".
In "The Book" I checked all places again where I use the terms "method",
"framework" and "approach", as already described below.
I don't use the term "approach" directly for PaR anymore, but e.g. for
"agile approaches" or "platform approaches" to not name specific ones.
I use the others either together as "methodical framework" or as
"PaR framework", but never "PaR method" again.
I added 2 pages for the dark side of PaR, where I explain what typically goes
wrong and that this can go wrong also with PaR, if you really want - but it is not that easy
with PaR ;-)
All documents (also The Page and The Slide) are updated to explain PaR as a methodical framework
in the benefits and in the texts.
They are online and thereby available for download now.
Also, I checked all PaR web pages and adapted as needed (mainly the PaRade and a new question
for this in the FAQ).
The thumbnail images of the documents are not updated yet because I also want to change the
titles to add "a methodical framework" (like e.g. on this page now).
Also the detailed PaRis needs to be updated once again because from the German translation
I figured out that "legal" should better be replaced by "laws" for
The Deck is available in German for download now, at least with the most important slides.
Therefore I broke the lines on the download page again.
Now it is Core, Helper, Presentations (new) and Tool Implementations.
I also updated the SWOT after exactly 3 months now, on the page of The Splashes,
in The Deck(s), on The Insert and in The Book (where the colors are different for printing):
"approach" is now also here a "framework",
"technicians" are now also here "developers",
"no risk" now is "low risk",
one "Supports" now is "Empowers",
"Abondons" now is "Dilutes",
"show ... diagrams" now is "makes ...diagrams",
I added the "dark side" and I changed some additional details.
What is PaR? It is a methodical framework - a systematic holistic methodical framework.
This now is the wording in Benefit 6.
Throughout The Booklet it is now either "PaR" or "the PaR framework" or
a "methodical framework", and in the German translation accordingly.
Next I have to update all other documents accordingly to make it consistent.
I got a license for Lucidchart from Lucid.app now, for drawing any kind of diagrams, also UML.
Thereby I created the draft of a more technical PaRis in UML, according to my newly defined
UML action relations (instead of SysML typical relationship relations).
I will discuss it further with Martin and Andrea and hopefully they will try an implementation
in ER and Capella.
This evening I joined the 3hr workshop of Scrum.org and Scrum.inc for the
of the Scrum Framework.
I wish it would have been more with Ken and Jeff, the minds behind, but I can understand
that they want to emphasize the community.
Afterwards I joined the 2hr Scrum Alliance DACH discussion about the main changes (I'm certfied
by Scrum Alliance since 2009).
Finally the Scrum guys understood that a project needs a Product Goal - funny, after many
made jokes at least over the last 15 years that the agile Scrum guys are working without
an overall goal.
This was always interpreted like "the agile guys do what they want", also ignoring
all processes, because they are "self-organized".
Therefore, now it is called "self-managed", the roles now are accountabilities,
the Scrum Master gets more responsibility and the PO is part of the team (what he always should
have been, but that's tricky when he is in the customer company).
I think that will help many, and in fact I was waiting for this focus on responsibility since ages,
because more and more critical projects started to apply Scrum.
And these moves also help me for PaR, which gives the processes more in the hands of the teams
by definition (pulling processes as requirements sets into the project, the ones they need when
they need them).
I'm looking forward to see the next 25 years :-))
The magic dashed arrow into TPL is gone from the diagrams.
I thought that the REG may get related templates also - maybe.
But it rather looks like they only request them and they are actually build in the COP.
Instead the HOW now has a relation to the REG.
The HOW always described some "regulatory notices" in the added notes, but the
relation was never shown.
Since it is very much effort to change all diagrams everywhere (it takes days in fact!)
I took the opportunity to do some fine wording and formatting refinements in addition.
All document diagrams are updated and available for download consistently again.
Now I have to adapt the text here and there, e.g. for the new relation in the just added
UML relation descriptions.
I am currently coaching a team of an automotive supplier that introduces ASPICE more
systematically for a project - but like always they start to get a dinosaur born and
already after just two weeks the processes, work instructions, guidelines, templates and
projects start to get inconsistent.
And they are just starting the overkill!
In the community session yesterday we had a very good introduction to Organizational Change
Management and KPI/Measuring from Sylwia - thanks again for that!
I took the notes on the fly in Miro - check the community minutes.
I also try to cover all of that in my chapter "PaRadigm shift", but it is soooo difficult.
"The Booklet" and the German "Das Heft" are updated as described
below and available for download now.
In addition I did some minor changes that you will not find ;-)
I rearranged "The Splashes" on the web page, from 4 and 2 in 2 lines
now to 3 and 3 in 2 lines.
Sounds trivial, but makes it look more similar to "The Booklet" where
I use the 2nd empty page at the end now for The Splashes with 3 lines having
I use the 1st empty page at the end now for the introduction of the chapter
"PaRadigm shift" from "The Book".
This is important because I realize more and more that people start easy and then
figure out that it is a real change.
Furthermore, after ordering another test print I moved some diagrams by a few
millimeters and changed some words again.
I also changed the text of the last "PaRdon ..." page and moved it to the
very end again, behind the 2 new pages (and it doesn't show up in the TOC any more).
So, "The Booklet" doesn't have any empty pages any more and now perfectly
fits on 20 pages (5 sheets of paper as brochure).
The measurement KPIs are now numbered, and the tool features also, like in
Good start working on "PaR - for Polarion" with Max Schmitt from IESE Fraunhofer
and on "PaR - for Jira with R4J" with Bernhard Doleschel from ease solutions
(see page "Downloads").
Community members can find the work documents in the MS Teams channel "6-under-PaR".
I am currently detailing in "The Book" the explanations of the required tool features.
Now I use the logo of the CC BY SA 4.0 license, linked to the website, see bottom left of this window.
On the page "Impressum / Legal" I link to the German and English websites alternatively, with
the small language flag for quick identification.
I further worked on the "merge/unite"-thing and almost all documents are updated and online.
I'm still working on "The Book" to explain it in detail and to make it consistent again in
the growing index.
Yesterday in the community weekly session "6-under-PaR" I explained my changes regarding
"merge/unite" and Andrea had the perfect idea to model the PaRis in an architectural
design tool (e.g.
also to clarify the UML relation types "aggregates",
"composes" and "implements" for PaR (see also the new frame on the miro
Working in miro with my new team license and the video chat there was really fine.
I hope that we soon don't need MS Teams anymore in those sessions.
The detailed PaRis now gets real cyclic arrows between the cascaded COP and Project box.
At the same time I replace the arrows between the cascaded TPL and Document, as well as
TEB and Team Members.
These rounded arrows now also have a new shade of gray ;-)
I now have described example item type fields in a table in the tool feature section of "The
I spent a whole weekend starting to create the index for "The Book", and while doing
so I figured out that I did not really use the words "merge" and "unite" with
the correct meaning.
Clearly: I swapped them in the challenges/solutions and benefits.
This is bad, because I wanted to use them dedicatedly by purpose, and now it is wrong.
This means that I have to change every (every!!!) document and diagram.
Good session with Max from IESE Fraunhofer about implementing PaR in Polarion.
I now provide the "Code of Conduct" also in German to end the discussions about the
interpretation of the English wording.
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
Once again refining the page "About us": adding Ease Solutions, structuring the
"Established business areas".
The other domains are not sharing the same web space anymore, but are true http
redirections now, configured on the hosting service provider side.
I also registered further domains for PaR (e.g. the short one ProAsReq.info).
Miro 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).
The board now only links to the CoC on the community web page "About us", instead of
duplicating the content.
Bernhard from Ease Solutions joins the PaR community and we want to implement a
reference solution of PaR for Jira with R4J.
I swapped 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.
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.
It is so important to understand the "PaRadigm shift" and to understand what
it means to establish it in a company.
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 (big thanks to Frank)
and added it to the page "About us" and to the Miro Meeting Board.
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.
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.
Working on chapters 4.x of "The Book", described Product Family Engineering with
a nice diagram.
I reviewed and reworked the chapter 4.2 (Cascading), 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.
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).
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
I also posted the 5th splash on XING.
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 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.
Posting The Splashes on XING in a weekly cycle.
Thanks to Martin from IESE Fraunhofer I can present the PaR approach at the
>re:WORK 2020 conference<
in Berlin 27.Sep-29.Sep.
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", updated the page for Downloads and changed the GDPR.
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.
I created a template from the "PaR - for Jama" and then copied and adapted it to become
the other new 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.
I have set up the Microsoft Teams PaR team and invited for the first PaR Community Weekly
"6-under-PaR" (getting it done on Monday for a 7-day-week ;-) including the Miro app also.
We're starting with 5 people out of 10 online on 07.Sep., exactly one month after going online with the
Now I reuse the diagrams as PDF instead of Office, due to tool enhancements.
Further reworking and refining the PaRis detailed map.
I got my new RØDE microphone, Logitech StreamCam, Logitech Capture app and the studio Soft
Light (with more than 100 LEDs) - see fotos on page "About me".
"The Deck" is new - currently containing 18 PDF slides that can be used in presentations.
"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<
as described in my
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
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.