Disciplined Agile Focused on Creating Hybrid Approach?
Michael SheaProject Manager| Children's Hospital of Orange CountyIrvine, Ca, United States
I was interested in getting scrum master certified. In reading about the Disciplined Agile series, it appears to be based on creating a hybrid approach from the start (in fact provides a tool kit to do so if I understand correctly). Is this the general premise of the DA programs, or is my understanding incorrect? Saving Changes...
Sort By:
Anonymous
Yes, DA sets out a range of different approaches, including the use of Scrum and Kanban. (the word *hybrid* is unfortunately much misused but in DA it has nothing to do with "waterfall") Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
DA is an "umbrella" you can use with any type of approach (Lean, Agile, etc) and any type of life cycle (waterfall, iterative-incremental, etc) and any type of method/framework (Scrum, XP, etc). I am writting this because I am using it (each time it applies) including before it was adquired by the PMI. Saving Changes...
DA's premise is based on the principle that context counts. Given that, no single recipe or limited set of recipes will fit a team's needs. So regardless of whether you are falling under a fully predictive, fully adaptive or hybrid context, DA provides you with choices and decision support to make those choices.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Oct 17, 2022 8:23 AM
Replying to Kiron Bondale
...
Michael -
DA's premise is based on the principle that context counts. Given that, no single recipe or limited set of recipes will fit a team's needs. So regardless of whether you are falling under a fully predictive, fully adaptive or hybrid context, DA provides you with choices and decision support to make those choices.
Kiron
Well said Kiron, totally agree with you. Saving Changes...
Michael SheaProject Manager| Children's Hospital of Orange CountyIrvine, Ca, United States
Appreciate all your responses, and I see you all use and support the DA model. My concern with it is, I learned in the ACP training when they discussed hybrid- that it has its place, but you really need to understand why one of the other standard methodologies 'doesn't' work for your particular circumstance (citing a lot of effort and validation went into them). What I'm struggling with is I can see a need to understand the methods before trying to modify them, and DA appears to be shooting to hybridize these methods right out of the gate without this consideration (I haven't taken the training yet so without that detail I am probably not qualified to make that statement, but is my initial impression and hence my question here)
...
3 replies by Keith Novak, Kiron Bondale, and Sergio Luis Conte
Oct 17, 2022 1:44 PM
Keith Novak
...
I would argue that if you are following any standard brand of agile, you are trying to do agile while not being agile. I call it "rigid agile". I often see that with consultants trying to sell their own brand, and people who took a course and think they are now experts.
The 2nd agile principle is embracing changing requirements. If your product changes based on the requirements change, why shouldn't the process?
If you take the DASM training, you will find that it primarily introduces you to a toolkit that helps you tailor your delivery model and WoW (way of working) to fit your needs. Deeper insight into the various lifecycles is left to you but later sections of the Choose Your WoW book explains them in more detail and their respective tradeoffs.
By all means, explore every prescriptive delivery model you can find and test them for their benefits and limitations. Then you can logically tailor the models to your own needs as opposed to trying to force them to work.
Oct 17, 2022 6:19 PM
Kiron Bondale
...
Michael -
there is no such thing as a "standard" methodology for agile. And few frameworks are designed from a project management perspective so some adaptation is needed (e.g. lack of a mobilization/initiation phase in Scrum).
You can absolutely follow a given framework in the context of DA - it is just giving you choices which are not offered by most frameworks.
Kiron
Oct 18, 2022 5:31 AM
Sergio Luis Conte
...
One of the missing tasks, at least what I saw along the years, is something that business analyst (BA) is in charge to doing (to put this in terms of PMI´s scope) before to start an initiative. It is call "needs analysis" or "strategy analisys" depending if you take the PMI or the IIBA standards on the matter. This activity is about to evaluate the current situation and the future desire situation to achieve to decide about the solution where solution is equal "the thing" to be created plus "the way" to create it. The way is where the approach, life cycle, method/framework, tools are defined. Just to comment about my compromise on that let me say that I wrote about that and I performed conferences about this topic from years inside the PMI World Tour. DA is an umbrella, you can use it with any type of approach, life cycle, method/framwork and tools. I am not a "DA Advocated" and I am not an advocated of something that do not best fit to create the solution after the analysis I mentioned before is done.
Appreciate all your responses, and I see you all use and support the DA model. My concern with it is, I learned in the ACP training when they discussed hybrid- that it has its place, but you really need to understand why one of the other standard methodologies 'doesn't' work for your particular circumstance (citing a lot of effort and validation went into them). What I'm struggling with is I can see a need to understand the methods before trying to modify them, and DA appears to be shooting to hybridize these methods right out of the gate without this consideration (I haven't taken the training yet so without that detail I am probably not qualified to make that statement, but is my initial impression and hence my question here)
I would argue that if you are following any standard brand of agile, you are trying to do agile while not being agile. I call it "rigid agile". I often see that with consultants trying to sell their own brand, and people who took a course and think they are now experts.
The 2nd agile principle is embracing changing requirements. If your product changes based on the requirements change, why shouldn't the process?
If you take the DASM training, you will find that it primarily introduces you to a toolkit that helps you tailor your delivery model and WoW (way of working) to fit your needs. Deeper insight into the various lifecycles is left to you but later sections of the Choose Your WoW book explains them in more detail and their respective tradeoffs.
By all means, explore every prescriptive delivery model you can find and test them for their benefits and limitations. Then you can logically tailor the models to your own needs as opposed to trying to force them to work. Saving Changes...
Appreciate all your responses, and I see you all use and support the DA model. My concern with it is, I learned in the ACP training when they discussed hybrid- that it has its place, but you really need to understand why one of the other standard methodologies 'doesn't' work for your particular circumstance (citing a lot of effort and validation went into them). What I'm struggling with is I can see a need to understand the methods before trying to modify them, and DA appears to be shooting to hybridize these methods right out of the gate without this consideration (I haven't taken the training yet so without that detail I am probably not qualified to make that statement, but is my initial impression and hence my question here)
Michael -
there is no such thing as a "standard" methodology for agile. And few frameworks are designed from a project management perspective so some adaptation is needed (e.g. lack of a mobilization/initiation phase in Scrum).
You can absolutely follow a given framework in the context of DA - it is just giving you choices which are not offered by most frameworks.
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Oct 17, 2022 12:58 PM
Replying to Michael Shea
...
Appreciate all your responses, and I see you all use and support the DA model. My concern with it is, I learned in the ACP training when they discussed hybrid- that it has its place, but you really need to understand why one of the other standard methodologies 'doesn't' work for your particular circumstance (citing a lot of effort and validation went into them). What I'm struggling with is I can see a need to understand the methods before trying to modify them, and DA appears to be shooting to hybridize these methods right out of the gate without this consideration (I haven't taken the training yet so without that detail I am probably not qualified to make that statement, but is my initial impression and hence my question here)
One of the missing tasks, at least what I saw along the years, is something that business analyst (BA) is in charge to doing (to put this in terms of PMI´s scope) before to start an initiative. It is call "needs analysis" or "strategy analisys" depending if you take the PMI or the IIBA standards on the matter. This activity is about to evaluate the current situation and the future desire situation to achieve to decide about the solution where solution is equal "the thing" to be created plus "the way" to create it. The way is where the approach, life cycle, method/framework, tools are defined. Just to comment about my compromise on that let me say that I wrote about that and I performed conferences about this topic from years inside the PMI World Tour. DA is an umbrella, you can use it with any type of approach, life cycle, method/framwork and tools. I am not a "DA Advocated" and I am not an advocated of something that do not best fit to create the solution after the analysis I mentioned before is done. Saving Changes...
INDUMATHI KANNAYIRAMPROJECT MANAGER| DELTASTAR POWER PROJECTS SERVICES LLCAbudhabi, U.A.E, United Arab Emirates
If you take the DASM training, you will find that it primarily introduces you to a toolkit that helps you tailor your delivery model and WoW (way of working) to fit your needs. Deeper insight into the various life cycles is left to you but later sections of the Choose Your WoW book explains them in more detail and their respective trade-offs.
I am interested to do DASM and waiting to pass a few more months Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
DASM is the best training to take. Saving Changes...
Community Champion
