Main Menu
Home / IT Governance / Legacy Support / Don’t Focus on the Final Product—Focus on Delivery

Don’t Focus on the Final Product—Focus on Delivery

It’s Finished—But Broken

A common situation: a new release goes out and several of the new features included don’t work—and the existing functionality is impacted by the failure of the new features. As the author of this article on ITIL and Me explains, many teams are far too focused on getting the final product out instead of paying attention where it counts: the process of delivery: 

Maybe I’m thinking about this topic because of my recent read of The Phoenix Project.  Maybe it’s in my head since I’m wondering how IT will evolve during the supposed impending IT & business singularity event.  Either way, the quality of a product can’t be tested right before production.  In fact, it can’t be tested in a single event, but things like quality assurance and governance have to be considered during the entire lifecycle, not just as checkboxes on a project management document.  This is where focus on execution needs to occur.  If a team is working efficiently and diligently, calling out flaws during each and every phase, be it an agile or waterfall build, then by the time the product reaches production, everyone can be comfortable in the end result.

5 Lessons to Keep the Project Working

From this point, the author shares fives lessons for teams who find themselves dealing with failures in the final product (and who wish to escape the redundancy of that problem). They include:

  1. Focusing on one thing at a time
  2. Minimizing the distraction of key resources
  3. Knowledge is power—and sharing is caring
  4. Go agile
  5. Go forth and fail

The third point in particular discusses the importance of sharing knowledge and making that sharing of knowledge standard operating procedure in your company. Make sure you have a knowledge database and that your team is able to navigate and contribute to. This helps with not only keeping your key resources distraction free, but also with stepping up the ability of your team to know what needs to be checked and tested during the development process—reducing the likelihood that key tests will be forgotten about until it’s release time.

Read the full blog post here:

About Matthew Kabik

Matthew Kabik is the former Editor of Computer Aid’s Accelerating IT Success. He worked at Computer Aid, Inc. from 2008 to 2014 in the Harrisburg offices, where he was a copywriter, swordsman, social media consultant, and trainer before moving into editorial.

Check Also

COBOL Is Still Around Because Nothing Better Has Replaced It

When COBOL was made in 1959, no one could have dreamed that it would outlive …

Leave a Reply

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

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time