There’s a popular saying that “numbers never lie.” It has a nice ring to it, but in reality, the adage requires that the numbers share a common language.
There are four service delivery and development approaches that any government project manager must know, given their increased popularity and potential to dramatically improve productivity.
To unlock your personal productivity and really get things done, you need a plan. Follow these five steps to make a weekly plan that makes your projects achievable and helps you be as productive as possible.
You can achieve better results in technology implementations by seeking the assistance of others and not trying to go it alone.
Government organizations at all levels are increasingly adopting agile development approaches like DevOps. Not only do these iterative, collaborative processes speed up delivery times for critical digital services and applications, they also meet unique public sector needs.
The purpose of software oversight is nothing more than to manage the risk of failure. The cost of oversight is more of the cost of risk avoidance.
Basic standards are the foundation to build more effective and innovative federal services for the future.
In this post we will extend our product lifecycle, adding detail that creates epics from themes, considering buy versus build, and cost. Finally, we will evaluate the options using four criteria.
DevOps has many different definitions. I define it as the standard framework or set of practices, processes and tools that development and operations teams use to deliver a service which produces a business value.
It’s a problem when an ambitious scope is used to justify a particular spend and then the scope is reduced to hit some deadline without reducing the cost.