DASA appreciates our participation in the DevOps Portfolio development
It was a great honor and great experience to review Devops Agile Skills association (DASA) Portfolio module.
Thanks to DASA organizers and fellow members!
Dear Respected Members of the Community Review Panel,
I trust this message finds you in good health and high spirits. I write to you on behalf of the entire DevOps Fundamentals team, expressing our gratitude for the contributions you have made during the recent review process of our latest DevOps Fundamentals course.
Considering time and logistical constraints, we had to limit the number of modules given for review. The breadth of feedback that we have received from you, each esteemed member of our community, on the modules of our course, has been both enlightening and invaluable. We deeply appreciate the time, expertise, and attention to detail that you have invested in ensuring the quality and efficacy of our content.
We wish to inform you that we have officially closed the review process and are now transitioning into the phase of meticulous incorporation of your feedback into the respective course modules.
It is our conviction that this initiative has not only served the enhancement of our course, but it has also forged an environment of collaboration and shared learning, which we hope has been equally rewarding for you.
Once again, we extend our deepest gratitude for your invaluable contributions. Your feedback has been instrumental in improving the DevOps Fundamentals course, and we are genuinely grateful for your support.
We will endeavor to keep you abreast of our progress as we proceed with the implementation phase, and we sincerely look forward to further opportunities of collaboration in the future.
Yours Sincerely,
Vijaykumar
Bill Dunkan on so-called “waterfall” projects:
The great explanation by Bill Dunkan on so-called “waterfall” projects:
“
Bill Duncan
Project management consultant and trainer. Primary author of the original (1996) PMBoK Guide.
Probably the MOST important thing to keep in mind is that there is no such thing as a “waterfall” project. Waterfall was defined by Royce in a 1970 article as a way to NOT do software development. Now, if you understand project management (which this AI bot clearly does not), you would know that there is such a thing as stage gate (also called phase gate) which is often called “waterfall.” But in phase gate revisions are NOT “costly and time-consuming” unless you leave them to the end. And that’s true for ALL projects. And the approach is generally “linear and sequential” but overlaps are both allowed and encouraged”