Popularized by Amazon, a Single-Threaded Owner (STO) is a leader who is 100% dedicated and accountable to a new initiative such as inventing a new product, launching a new line of business, or executing a digital transformation. The Single-Threaded Owner is responsible for turning strategy into real results.

A Program Manager is responsible for managing multiple interrelated projects and ensuring that - taken together - they produce specific business outcomes and benefits for an organization. 

The title "Program Manager" is not very common. Organizations have Project Managers, Product Managers, General Managers. But "Program Manager" is rare. This is because often executives and middle managers play the role of Program Manager even if they don't have the title.

AI/ML has the potential to deliver incredible value to customers. A single breakthrough can make a product company's growth soar. A fine-tuned model can completely transform an enterprise's operations.
​
The mechanics of delivering such a program are very similar to traditional projects on the face of it, so it is tempting to think of the implementation as being the easy part. But because of the non-deterministic nature of AI/ML, all the pitfalls of ordinary software development programs - misaligned objectives, underestimation, lack of process, skimping on QA, ignoring risks, etc. - are amplified x10. To deliver successfully, you need to ratchet up the program diligence.

Studying for the PMI-ACP agile PMP exam? For this test you not only have to understand and have lived agile processes, you have to remember a lot of terms: names of techniques, collaboration games, lists of principles,  etc. Here is a cheat sheet to review before the exam, to help answer all the trick questions. 

I've also included a comprehensive inventory of free PMI-ACP online tests, over 1,400 questions in total. With a cost of ~$400 for this test, it is definitely worth going through all the free mock exam material to make sure you are thoroughly ready. Good luck!

From research and prototyping to commercial development, AI/ML requires making decisions and trade-off's. This is where the PM needs to provide loads of context to the R&D team: what are the customer problem(s) are that we are trying to solve? What parameters and trade-off's would be acceptable to a customer? Have we considered the cost trade-offs of operating in practice? ​

One of the biggest challenges of modern software creation is having multiple team members — product managers, UX designers, data scientists, software developers, QA — working in parallel rather than sequentially. The world would be a much simpler place if the Product Manager completed a detailed requirements definition, then handed it off to data scientists who prototyped and refined their algorithms, then handed off to UX designers to create the full design, who then handed it off to development to build, who then handed off to QA for testing. 
​
Unfortunately this is not the world we live in. Every software initiative is a race to getting value into the hands of users, and building sequentially is not an option. 

​​Moreover, teams are continually learning and need the ability to iterate. Product managers keep getting fresh market intel that needs to be injected into the product, data scientists keep making breakthroughs in the predictive algorithm’s accuracy, designers keep refining based on user feedback. The name of the game is agile, iterative, and mass parallelization of teams. 
​
But how do leaders run all of these very different teams that depend on each other in parallel, and still deliver to market fast?

If you are interviewing a vendor or issuing an RFP to develop custom software for the Enterprise, there are numerous program, training, support, architecture, and security requirements that any Enterprise-grade system should have. Here is a checklist of questions to probe any vendor about the maturity of their enterprise software development approach end-to-end.