Mohan KulkarniPM Specialist| MBK ConsultantsPune, Maharashtra State. India, India
I read Preface and forward of the book WOW. I am yet to read the book.
My first impression is "is there anything new-not known?"
we all know through the PM and Agile Principles and practices that
"time keeps changing-so the environment-so the needs-so the aspiratons-so the team -so the team members -so the culture - so the practices.Therfore if one or PM and Project team and PMO has to succeed in succcessful delivery as DOD (which also may undergo change) ,then the architecture of the project management process as well as all the concerned shall be flexible, agile , quick, adaptive and shall have tenacity and resilience to sustain , plan and succeed"
If that is so what is different and greatin DAD?
But if somebody has gone through WOW completely ,would like to know the views and differentiators.
Mohan Saving Changes...
Sort By:
Milena IlievaProgram Manager Global accounts| VMWareVienna, Austria
Hi Mohan,
I may have missed something is the publications, can you please clarify the abbreviations which you used - WOW, DOD, DAD, and what are the sources?
Thanks,
Milena
...
1 reply by Rami Kaibni
Jun 28, 2020 12:16 PM
Rami Kaibni
...
Milena
WoW = Way of Work
DAD = Disciplined Agile Delivery
DOD = Definition of Done
RK
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
If you do not try to work trying to use agile approach you will not understand it. The key value in DA (I am not saying it today, I use DA from the time it was created and not only DA, I am using the whole "suite" which was created by @Scott some of them with other people) is it is focused on architecture and it is totally independent of the method/life cycle you use. For example, I have successful implementations of agile practices using waterfall life cycles because the type of product demands to use waterfall process or inside organizational structures which were hierarchical because the environment demands to be that. Just to add information, people like Tom Gilb or Alistar Cockburn created other works that can be used in the same orientation but when Scott published his work it was a more consistent "glue" with a more consistent level of "abstraction". Adding to add, the differentiation DA make between Lean and Agile. My concern today is it seems to me, just a perception, DA is loosing that when created things like Lean-Agile-Scrum something. I hope the value of DA will be not loose because the pressures PMI could put on "making business" (just to clarify I am not using the word business in a pejorative way. It is nothing "bad" for me on that). Saving Changes...
The benefit of DAD is for teams who are trying to be more agile within an enterprise context, it provides a basis for "guided continuous improvement" of their practices which is superior to trial and error (the normal method by which teams improve).
Unlike frameworks and methods, DA provides choices in terms of roles, life cycles, practices and approaches.
Community Champion
