The Iterative Engagement Model


Hello, my name is Mikhail Papovsky and I’m the CEO here at Abraic. One of the most critical reasons so many IT projects are so unbearable is those vendor contracts. Those documents are long and complicated, but in the end they simply say that a vendor will deliver a certain scope in so many months. The chances that the scope is what you will actually need from the vendor in the course of the project are pretty slim. We have all been there, wasting time on contract negotiations, change orders, and supplementing using under vendors. Wouldn’t you love to spend all that time and energy actually working on the project? There is a better way though: an iterative engagement model. This is where you, the customer, commit to use a vendor for short iterations, usually 2 to 4 weeks. During these iterations, you ask the vendor to execute the most critical tasks, the ones that will have the highest impact. During the first cycle you would come up with a general plan of attack, which we usually represent as a backlog of opportunities both large and small. For each of the following cycles, top impact opportunities from the backlog are selected and completed. Each of the 2- to 4-week iterations is long enough to focus on producing measurable results. At the same time iterations are short enough to allow for dynamic changes to the plan, priorities, or even intensity of the effort. No need to renegotiate those daunting contracts. You’re welcome! There’s no better “risk with a vendor” model. If we, the vendor, don’t perform, we just wouldn’t be rehired for the next iteration. It’s that simple. Only those consulting organizations that are confident enough in their ability to deliver outcomes at a predictable cadence can afford to offer the iterative engagement model. Abraic is a stellar example of such an organization. Give us a call or email us to learn more.

Add a Comment

Your email address will not be published. Required fields are marked *