PaR - Processes as RequirementsFAQ

FAQ - Frequently Asked Questions


Table of Contents

   "Why do you need a FAQ? Is PaR not described thoroughly?" >Answer<

   "What are the vision and mission behind PaR?" >Answer<
   "So what actually is PaR?" >Answer<
   "Is there a viable business model to commercialize PaR?" >Answer<
   "Why should I NOT apply PaR to my business processes?" >Answer<

The Book
   "When will The Book be available?" >Answer<
   "Why is the PDF copy of The Book personalized?" >Answer<
   "Why are the printed copies of PaR so expensive?" >Answer<

  ?   "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 are the vision and mission behind PaR?"  
   !    I do not really like this vision/mission stuff, 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 cost some money. When you need consulting or support, then you may contact me or people from the PaR community to book them for these services - check the page "About us" 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.
  ?   "When will The Book be available?"  
   !    When it's done ;-) It's quite a lot of work and I have new ideas every day. My backlog still feels larger than the book itself. Meanwhile, if you want to get the current draft as PDF simply follow the steps as described on the page "How to buy" (just leave out the part with the receipt). Some companies that are currently implementing PaR requested the PDF this way and I keep them in the loop with updates. There (and on the Downloads page) a Teaser PDF is also available that shows some interesting pages of The Book. I also added an extra page "Book vs. Booklet" to explain why both exist and how they differ. The community members find a regular updated PDF in our Microsoft Teams channel "6-under-PaR".  
  ?   "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 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. That's also the reason why you have to wait 8-10 days for your personal printed copy. But I want to offer high quality in print for high quality of content. 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 ;-) I also hate those "optical" prices and therefore it is not 9.99 but 10.00 EUR. When you buy it from your local bookstore or Amazon I finally get 1,97 EUR after VAT. Is that too much? When The Book will end up with maybe 300 pages and I go for glossy color hardcover with the same paper quality in color, then it will be 100.00 EUR and I finally get about 10.00 EUR after VAT. 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 100.00 EUR? That's less than one hour for a consultant and less than two hours for sitting in a training. And please have in mind that I have just spent nine months fulltime on PaR until publishing The Booklet at least. So, come on and order 10 of them for your friends and colleagues, together with 10 of The Mug ;-)