Delivery Challenges Blog Series
Every technology project starts with an outcome—a business goal that needs to be achieved. But to achieve that goal, you need to define a set of deliverables, establish a timeline, and determine a budget. Rarely do the timeline and budget line up with the work that needs to be done. There are seldom enough dollars to put the number of people on the project necessary to bring the deliverables to life within the timeline. This is often because of how challenging it is to fully scope a project up front. No matter how thorough you are, new requirements come to light, resulting in scope creep.
Many companies will lean into project management to make everything come together. Smart—a solid PMO practice is the foundation on which all successful technology projects are built.
But you can’t always project manage your way out of this type of problem. That said, there are some things you can do.
Two Key Approaches to Use When Time and Budget are Out of Sync with Project Scope
One of the most complex technology consulting programs I’ve worked on was for a new company in the healthcare space. The budget was a swag from an investor’s presentation deck and was completely out of alignment with the six-month timeline for standing up ERP manufacturing system, provider and patient registration and management portals, and an ecommerce app. Rescoping the project wasn’t an option—if every compliance parameter wasn’t met within the given timeframe, the client would have to wait an entire year to reapply with the organization that had program oversight. In the end, we met the timeline, stayed on budget, and our client was awarded the contract they were after.
We used two key approaches to make it happen. First, we brought all the right stakeholders to the table early to develop standard operating procedures (SOPs). And second, we used those SOPs, as well as compliance guidelines, to build and validate wireframes before standing up MVPs. Then we validated those before coding the actual apps.
Engage the Hive Mind
At the beginning of the initiative, we brought all the key stakeholders together for a series of workshops—one for each app we had to deliver. Every department that had a say was represented—product, engineering, sales, marketing, manufacturing, and legal. Not only did we have a binder on hand detailing hundreds of pages of compliance regulations, but we also had someone on hand who knew them inside and out. Collectively, we walked through every aspect of each app, developing standard operating procedures, strawmen, and requirements.
This hive mind approach meant we could problem solve, make decisions and come to agreements at speed and minimized our chances of going down the wrong path.
My Take
When timeline and budget aren’t in line with the work that needs to be done, you can’t afford to make mistakes. Get the people who hold the answers to your questions in a room and map out your requirements. At Kopius, we call these JumpStarts, and they may take a few days or a few weeks. Then, continue to check in with the same stakeholders at every critical juncture to validate your work.
“Measure once. Cut twice.”
For me, the project management equivalent of “measure once, cut twice,” is wireframes first, MVP second, coding third. And at each of these stages, you need to bring your stakeholders together to validate your work. For the healthcare project, once we had a thorough list of requirements, our UI/UX developed wireframes that we validated with the same group of stakeholders we initially brought to the table. This allowed us to identify and work through any potential issues up front. Then, once the wireframes were validated, we stood up MVPs for each app so stakeholders could walk through the basics of each process and validate it. Only then did we dive deep into coding all the features and functionality for the first release.
My Take
When timeline and budget aren’t in line with the work that needs to be done, the inclination can be to jump right into coding. A better approach is to double down on validating your path forward through JumpStart workshops and wireframing. This will minimize errors—and added time and costs—in the long run.
Expect the Unexpected
No matter how thorough you are in developing your requirements, there are going to be some “ahas” along the way. You have to expect the unexpected and remain flexible. But being flexible doesn’t mean saying yes to everything. Scope creep can derail a project from both a timeline and budget standpoint. For this project, we managed that by getting everyone to agree to a light phase one for each application, then planned to iterate, releasing new features every two weeks after launch.
Looking Ahead: The GenAI Approach
Like many technology companies, Kopius is actively integrating generative AI (GenAI) into our processes, and I’m working on a set of custom GPTs that I believe can make a difference when time and budget are out of sync with requested deliverables. By entering business and technical requirements into it—maybe even a transcript from a discovery session—and asking it to generate common use cases that serve as starting points for designing application features, we can streamline the work involved in building new apps. The prompt engineering requires a lot of up-front effort, but once that initial lift is done, we’ll be able to use it again and again.
Undoubtedly GenAI will deliver thousands of small efficiencies like this, but it’s only part of the equation. The time / budget / scope challenge is an inherent part of software development, and solving it is always going to take a multi-faceted approach.
JumpStart Your Technology Project—and Stay on Track—with Kopius!
At Kopius, we harness the power of people, data and emerging technologies to build innovative solutions that help our customers navigate continual change and solve formidable challenges. To accelerate our customers’ success, we’ve designed a JumpStart program to prioritize digital transformation together.
