Hi Allison, >From my perspective, having experienced both Waterfall and Agile, the maturity model can be used for Agile projects because Agile naturally lends itself to *increased collaboration / increased inclusivity / increased transparency *because it has a built-in feedback cycle, and shorter cycles making the timely sharing of information more important. In particular, the feedback cycle was originally included so that (as you are probably aware) projects were able to capitalize on quick feedback from customers to guide planning and other PM processes. So it was actually intended as a feedback cycle *external *to the organization but the philosophical "dye was cast", so to speak -- in Open, anyone can be a stakeholder and have their feedback included -- hence Agile has a natural alignment to the open organization and the inclusion of perspectives of customers, associates, and others.
Although Waterfall doesn't have the iterative customer feedback cycle there can still be enactment of open values. Most of the organizations I've worked at would be between a level 1 and 2 depending on the open value in the maturity model regardless of the method of project management that they used. The net, for me, is that one could have a closed Agile process (eg with little transparency, no meritocracy) and an open Waterfall process dependent more on the type of organization than on the project management system. I hope this helps! If it does, I'm happy to chat more. Heidi On Mon, Jan 29, 2018 at 10:28 AM, Bryan Behrenshausen <[email protected]> wrote: > On 01/29/2018 10:09 AM, Allison Matlack wrote: > > You might remember me asking you late last year to review a one-page > > version of the maturity model... > > > > Thanks to Bryan's help, we've now got a PDF version on GitHub for your > > use, review, and comments: > > > > https://github.com/open-organization-ambassadors/open-org-definition > > Thanks so much, Allison! This is a fantastic resource and much appreciated. > > > It's only available in PDF right now because (as Bryan tells me) getting > > an editable version of a precisely configured table has proven > > difficult. If anyone want to attempt it, please feel free. > > I should note that this has "proven difficult _for me_," but I'm sure > someone possessing more knowledge of GitHub and markdown could tackle it > with ease. I've opened an issue [1] related to this situation so we can > 1) more widely seek help with it and 2) track our progress toward > resolving it. > > Bryan > > ----- > > > [1] > https://github.com/open-organization-ambassadors/open- > org-definition/issues/19 > > _______________________________________________ > Openorg-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/openorg-list > -- Heidi ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Heidi Hess von Ludewig Interlock Product Manager Customer Experience & Engagement Local time - US EST (Raleigh, NC) IRC: heidiHVL email: [email protected] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________ Openorg-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/openorg-list
