Why PMWay?

PMWay: The Way to Project and Process Management Excellence

Why PMWay?
  • I built PMWay to underpin an ICT MSc. Dissertation. 
    The use of the PMBOK as a foundation in PMWay is based on my appreciation of the fact that the PMBOK has status as a Standard grouped along with the ANSI, ISO and BS Standards.

    If you have a different (better) understanding please send it to PMWay

    The above said, I am constantly amazed by many I speak to who totally disregard the above "state of affairs," while fanatically insisting on hyping on and on about agile!  One person said to me, when I explained that agile was not on the above Standards, Frameworks matrix: "Yes but how old is your diagram?"  I thought to myself, "Your point taken and rejected, my point (if you look carefully at the Standards Frameworks Landscape) totally misunderstood by you!"

    Don't get me wrong. I love agile and especially Scrum:  But only If well run using the Scrum processes that are defined and operate at CM Level 2+!
    (With lapsed traditional project management controls that very often occur with agile, it will have to be run very well (regularly demonstrating and releasing working software) to mitigate serious risks associated with agile's loose approach!) ELSE AGILE IS NO BETTER THAN BADLY (CM L1) RUN TRADITIONAL PROJECT MANAGEMENT!

    A deeper look at the section in PMWay on Scrum here
    will clearly explain why processes should be correctly used at Capability Maturity Level 2+ for success; which (if you joint the dots at the bottom of the home page) will also explain what this web site is all about. 
    Operating at Capability Maturity Level 1, especially with agile, must surely be, as I often see, from a project management perspective, a recipe for disaster!
    Following the SBOK (Scrum Body of Knowledge) processes more closely on the other hand will greatly assist in improving the agile (Scrum) project's success rate!  Appreciating the PMBOK processes (mindful also of joining all the dots found on the home page) as a "best way to run projects," when using agile must further reduce risk and waste while improving productivity and quality.
    Take the PMWay pin test now if you want to ascertain your application of project method and associated risk exposure.

    This image below, from the PRINCE2 agile manual, in my mind succinctly illustrates that while agility is awesome, it must not come about at the expense of well engineered software solutions.
    PRINCE2 Agile
    (If interested click the image above to jump to an excellent talk about the death of Agile (with a capital A); from one of the guys who attended Snowbird in Utah and gave us the agile manifesto)

    Therefore, because I appreciate the PMBOK's value to assist me to run my Programs and Projects better, in the interest of project management process improvement, you are welcome to use the assets you find here.

    Note:  Unlike Business As Usual (BAU) a project is a temporary undertaking! 
    Again I am consistently amazed at companies who bundle what are essentially project management processes into BAU!?
    They also appear to be bundling the SS, SD and ST ITIL processes into BAU (essentially SO) stating that DevOps is a replacement for ITIL best practice!?
    It is obvious to anyone who understand the ITIL processes that SS, SD and ST processes exist in the project management domain and are intended to assist the organization to "mind the gap" / "avoid getting stuck in the tar pit."
    In essence (via the project) you are "jumping a gap" from one baseline to a new (improved) baseline which import, if lost, means that the organization essentially will surely get stuck (lost) in the tar pit.

    Also, from a P3O perspective the project can be run alone or as an essential building block of Portfolio's and Programs.

    And from the perspective of the project itself, scheduled TAsks (Time Asks) are the essence of project management. 
    (This truth is found in processes 4.2, 6.5, 4.3, 4.5 in the PMBOK 6 Dashboard.  Can you see it?)

  • PMWay explains a sure way to implement process improvements for higher Capability Maturity levels to increase Productivity and Quality.
    At the same time focus on process improvements will reduce Risk, Rework and Waste!
    Capability Maturity Level 2 (CM L2) is all about Project Management processes.  CM L2 automatically installs "Good Governance.

  • The Project Management Body of Knowledge version 6 Dashboard (the matrix / asset found on the PMWay home page) is:

    "the beating heart (as primal source and power center)

    for the collated knowledge found in the PMBOK"

    Using this Dashboard you can easily access all the PMBOK Processes, and thereby, each of their *ITTO's found within the Guide. 

    *ITTO's are: Process Inputs, Tools and Techniques and Outputs - for each of the 49 PMBOK processes on the Dashboard.
    Processes (and their ITTO's) are used from the beginning (INITIATION) to the end (CLOSURE) of a project (cross referenced by Knowledge Area), at each step of your project management journey and form a well defined method (you can think recipe with essential ingredients) for project management success.

    When logged in:
    All of the 49 processes and their ITTO's are accessible via drilldown off the PMBOK Dashboard.
    When logged in: PMWay has a teaching section specifically focused on how to use the Dashboard (with visual teaching overlay over the Dashboard) showing you exactly how to use this asset to run projects successfully at Capability Maturity level 2.
    When logged in:  Many web pages consolidate PMWay detail into a possible strategy / vision to achieve Capability Maturity L2 which you are welcome to peruse. I.e. while agile is often touted as the panacea, PMWay knows that agile (or any project methodology), badly run at CM L1, does not have what it takes to eliminate the chaos.
    PMWay members (which is optional): can use elevated access and drill down deeper into the Dashboard to the PMBOK Guide as, under my auspices, I am thus enabled by you to assist you (via your registered email) as a student seeking PMP, ACP or CAPM exam preparation advice. I can also assist you in a general consultative capacity to achieve project and process management excellence.
    For the scope of my consulting advice (and assistance with PMWay resources) you are invited to "join the dots" from the home page.
    Click "Contact" on the menu bar at the top of the home page to sign up.

  • Using the functionality of the PMBOK Dashboard in particular means you can use, practice and improve your grasp of the PMBOK version 6 processes (along with the associated ITTO's of each), as essential knowledge needed to:

    1. Pass the Project Management Institute (PMI) Certified Associate in Project Management (CAPM) exam or,

    2. Pass the Agile Certified Practitioner (PMI - ACP) exam or,

    3. Pass the PMI flagship certification - the Project Management Professional (PMP) exam. 

    4. Gain a solid knowledge of project management processes, their ITTOS, their implantation order so, with common rules of the game mutually agreed and understood, you (and team) can run projects better.  You can also use the Process Selector Wheel to check if you know what Process Number applies to what Process.  This is a fun way to get to know and learn the Processes.

    5. Signed up members can use the Notes Section provided below each process in PMWay to log all your ideas to tailor these processes.
      The art of effective tailoring within the PMBOK is found within the processes and knowing what and why ITTO's should be included in your project (to what detail) or why not. The ability to log these decisions (from an audit perspective) is a key and crucial requirement of a project management professional which is facilitated by these notes!
      To this end we must always ensure that projects are kept sweet and simple, lean and agile, and that an achievable set of goals for the team is rapidly created for them to rally behind and deliver against.
      I.e. While (when) BEST PRACTICE is understood, BEST PRACTICAL (from an agile and lean perspective) can be better!

  • And, if you plan to use agile, you can now run these projects underpinned by the logic of the 'fully agile compliant' PMBOK 6 Dashboard above. 

    It is a fact, in the sixth edition of the PMBOK® Guide, each knowledge area contains a new section entitled Approaches for Agile, Iterative and Adaptive Environments.  For a specialized qualification in agile consider the PMI Agile Certified Practitioner (PMI-ACP).  This formally recognizes your knowledge of agile principles and your skill with agile techniques (including XP, Scrum, Lean and KanBan etc.).
    If you think that the PMBOK is outdated because it is "waterfall," I challenge you to work through the PMBOK "How To" (from the main menu). If you do this then I believe you will come to understand that your assumptions are incorrect and do not fully grasp all the pertinent issues. To illustrate why I say this take the pin test now and ask yourself honestly:
    where is your game really at?pin

Click here for the changes in PMBOK version 6 when compared to PMBOK version 5.