| |
| |
FAQ - Frequently Asked Questions
|
|
| |
General |
|
| |
?
|
|
"Why PaR?" |
|
| |
!
|
|
When you need to develop projects according to processes (due to regulations,
due to monitoring and predictability, or just to manage complexity)
then the first documented processes may have been good help.
But one day you may discover that they have grown extensively and rather became overhead than help.
And when you are used to develop according to straight requirements instead of epic documents
then you may ask yourself why only the "what" is described as requirements,
and not also the "how".
This was the starting point for me years ago to develop an approach to describe Processes as Requirements.
So, when you don't need to work according to heavy processes in complex projects
and when you are not working according to defined sets of requirements, you either will not need
PaR or you simply will not like it.
Don't apply a solution when you don't have the related challenge!
When you have the "PaRade of challenges" that I describe, then PaR may be a solution.
|
|
| |
| |
?
|
|
"Why do you need a FAQ?
Is PaR not described thoroughly?" |
|
| |
!
|
|
The methodical framework PaR itself is described thoroughly in the documents that are
available online, but people ask a lot of questions about the organization or the community when
I am consulting companies, presenting at conferences or discussing in any online sessions.
Those questions don't belong to the methodical framework itself and the answers may also vary over time.
Therefore, I created this FAQ page to answer them here once for all.
|
|
| |
| |
?
|
|
"What is the idea behind the PaR
community?" |
|
| |
!
|
|
I learned that when I consult companies and coach teams I see much more projects in the same
time and can transfer learnings from one to the other much faster.
A community of multiple experts, consultants and customers can learn even faster when they have a common
topic or challenge.
Therefore, I am sure that we all together can improve PaR much better and faster then I could do alone.
We saw same effects for architectural design, for Scrum, for functional safety and for many other topics.
So, if you also want to improve bringing standards and processes into project teams and to support working
self-organized within departments, then please join our community and help us - for sure you will also
learn something from the others.
|
|
| |
| |
Business |
|
| |
?
|
|
"What is the vision & mission behind
PaR?" |
|
| |
!
|
|
I do not really like this vision & mission stuff, because often it restricts being agile,
but well, here we go:
My vision is that project teams are not working according to project processes,
but in project processes, improving them from team to team and from project to
project via a process platform.
My mission is to improve and provide PaR as methodical framework to help project teams
and companies creating real process platforms and to coach them uniting process platforms with product
platforms, ideally by establishing an intrinsic and holistic component model.
Now you know it - now measure my work against it ;-)
|
|
| |
| |
?
|
|
"So what actually is
PaR?" |
|
| |
!
|
|
I consider PaR being a methodical framework, precisely (as stated in
benefit 6) a systematic holistic methodical framework.
PaR at large is not a method by itself and also not a process.
You can find a lot of dedicated methods within the framework, and that is why I call it a
methodical framework.
Nonetheless I don't describe PaR as a box of methods yet.
It would be more systematic but also even more complicated.
This may either come with a next version of PaR or as a chapter in The Book.
The only "process" I can imagine for PaR itself is a kind of transition process for
a corresponding project to set up the framework and then transfer content from the old existing
framework to the new one of PaR.
This in fact is also one of the points in my backlog of the book.
|
|
| |
| |
?
|
|
"Is there a viable business model to
commercialize PaR?" |
|
| |
!
|
|
It is not intended to commercialize PaR as methodical framework.
It is rather provided under CC BY-SA 4.0 license, as described on the page
"Impressum / Legal" in German and English.
Thereby the PaR methodical framework itself is provided for free and can be used commercially also.
So you can make your own business model around it.
This also simplifies applying it in large companies: You don't have to ask the boss or the purchasing
department for budget, you don't need to obtain with the legal department any license for the method,
and you can apply the existing RE tool, so you also don't need to ask the tool guys for setup.
At least The Mug and The Book are already commercialized (by me).
Trainings, workshops, consulting, or support may be offered and are partly already available from people
of the PaR community, to be booked according to the pages About us amd The Education.
When you want to offer predefined requirements sets or support for certain tooling, then simply get in
touch with me and the community to get help.
|
|
| |
| |
?
|
|
"Can I get professional support in
any form?" |
|
| |
!
|
|
PaR as methodical framework is provided under CC BY-SA 4.0 license, as described on the page
"Impressum / Legal" in German and English, so it's provided without costs also.
There is lots of material (website, PDFs, PPTs, videos, prints) available and you can get into it in an
autodidactic (self-paced self-educated) way.
When you want training, workshops, consulting, or support in addition, then you may contact me
or people from the PaR community to book me or them for these services - check the pages
About us, The Education, and ask me or them for the needed budget.
When you want to buy predefined requirements sets for certain tooling, then you may also check if you can
buy it from people in the community - it will still be cheaper than creating it yourselves.
|
|
| |
| |
?
|
|
"Why should I NOT apply PaR
to my business processes?" |
|
| |
!
|
|
Business processes for organizations are rather small and simple.
Production processes for factories need to be very predictable and repeatable.
Development processes for complex projects shall be very flexible and have to provide proof
of compliance.
And that is where PaR has its strength.
Complex development projects also have many functional and technical requirements anyway,
from market level via product and system levels down to domain levels.
Therefore the projects work with requirements management tools anyway.
And mapping functional and technical requirements with procedural requirements helps a lot.
So, if an organization or factory has similar aspects, e.g. strong regulatory standards that
must be proven for compliance, many stakeholder requirements, necessarily high
flexibility, measured coverage of process application, then it may make sense to apply the
methodical framework PaR also there.
But I think this is rarely the case.
|
|
| |
| |
The Book |
|
| |
?
|
|
"Why is the PDF copy of The Book
personalized?" |
|
| |
!
|
|
Also The Book is under CC BY-SA 4.0 license, as described on the page "Impressum / Legal"
in German and English.
Thereby, you may pass on the PDF to others or print it.
But according to the license you are responsible for doing this accordingly
(means: if you pass on the PDF to colleagues, then it is fine, but you should not offer it for
free download or sale on the web).
I mainly want to know the entry points of the PDF distribution, so that I can send updates or
additional infos from time to time, that you then please distribute in the same way as the PDF
(if you did so).
|
|
| |
| |
?
|
|
"Why are the printed copies of PaR
documents so expensive?" |
|
| |
!
|
|
Well, are they?
It's not Harry Potter, it's a very special technical document, so I'm not going to sell thousands of them.
Therefore, I decided to go for self-publishing with print-on-demand.
This also enables me to stay agile and to improve the paper continuously.
And thats also the reason why you have to wait 8-10 days for your personal printed copy (or you ask me
for one that I have in stock or with me in my car).
The Booklet is just 16 pages content, but printed on 150g glossy color paper with a glossy colored cover
front and back.
So I really think it's worth it from the material and publishing side.
It feels good to hold it in your hands.
And if you don't want it, then just go for the free PDF and print it yourself
(but paper, ink and time will cost you more ;-)
The Book is 180 pages for 49 EUR.
To be honest: If you work on PaR for two years, introduce it successfully to your company, have a lot
of fun with it, and together with your project teams save tenth of thousands of Euros due to higher efficiency
over the next years, then what is an investment of 49 EUR?
That's less than 20 minutes for a consultant and less than one hour for sitting in a training.
And please have in mind that I have just spent nine months fulltime on PaR until publishing The Booklet
and another two years until publishing The Book for the first time.
So, come on and order 10 copies of The Booklet for your friends and colleagues,
together with 10 pcs of The Mug and at least 2 copies of The Book.
|
|
| |
| |
?
|
|
"When update?" |
|
| |
!
|
|
For The Booklet I still don't see the need of an update.
It is written on high abstraction level by purpose and the big changes to PaR didn't come yet.
The Book was - of course - not really fully completed when published.
It was well crafted - as far as I think - and complete enough to go for it, but I still have a long
backlog, lots of ideas, and I'm also gathering lots of examples from pactice.
So there will be an update, and it might be end of the year again (2023 or 2024 ;-)
|
|
| |