At Inverted Software we pride ourselves in our unparalleled success rate, and while, according to the Standish Chaos Report 68 percent of technology projects is “improbable” meaning it failed, time and time again we keep delivering successful projects to our happy customers.
If you are struggling to understand how to measure success or if you are trying to demonstrate your software project was successful, the four questions below are internally used at Inverted Software at the end of each project to measure ourselves and make sure we bring true value to every customer.
Was Your Project Delivered On Time?
Every project needs to have a defined timeline. The timeline is an accumulation of the requirements gathering, development sprints, quality assurance, user and acceptance testing and deployment to production systems.
Prior to the discovery phase, projects should have a T-shirt size estimate, meaning, an estimate that is a best guess and is based on experience.
Your software vendor can estimate this for you as chances are, they are highly experienced at ground up development projects. After all, they do this for a living!
After the requirement gathering phase is over, your technical architect, along with the project manager can estimate and compose the sprints.
At this point the project’s overall timeline should be set more accurately with a 10-15 percent margin of error considering the allocated resources.
Was your project delivered on time? Mark your checkbox!
Once you have estimated your timeline, you can establish a budget.
Was Your project Delivered Within the Budget?
As your project’s timeline was set at a 10-15 percent margin of error, so should your budget.
Your budget should be time material based.
Any fixed bids you might get from a software vendor will always be based on the lowest quality and quickest timeline.
This means cutting corners, bugs, performance and maintainability issues that might make it difficult or even impossible for the finished product to satisfy your users.
No one wants to wait thirty seconds for a screen to load.
Most companies leave a 30 percent buffer between the project estimate and the actual cost.
This accounts for resource de-allocation, communication errors and other miscellanies issues that might arise.
Was your project delivered within the budget? Mark your checkbox!
Did Your project Satisfy the Original Requirements?
Look at the project’s PRD (Product Requirements Document)
Now is the time to compare the final product to the one your product manager conceived.
Are the screens identical? Does the functionality match the user stories?
What about browser and device compatibility?
The final test is the load test. Did your product perform according to the specifications?
If everything passed, mark your checkbox!
Did Your Project Solve Your Business Need?
This is the most important aspect of every software system and the reason it was built to begin with.
Every enterprise system is created to alleviate a pain point in your business and to make your processes more efficient.
It does so by helping users be more productive and automating manual work.
Is your system a true asset to the business? How much resources effort will it save your business during its lifetime?
If the answer is: More then its cost, then yes, your system did solve your business need and is well worth its investment.
Software is there to help our daily lives and your product does just that so mark your last checkbox!
Yes, most software projects fail, but, yours doesn’t have to.
Just keep in mind those four questions and use them to measure your software project’s success.
If you delivered on time, on budget and demonstrated true value for your company, your project is successful.
Need help in delivering your next project successfully?
Inverted Software delivers software using our teams of developers, QA, Architects, Solution directors and more.
Contact us at: Contact@InvertedSoftware.com