7 Questions to Ask When Developing a Solution

Lonnie Pacelli is an Accenture/Microsoft veteran with four decades of learnings under his belt. He frequently writes and speaks on leadership, project management, work/life balance, and disability inclusion. Reach him at [email protected] and see more at ProjectManagementAdvisor.com.

  Product Management   Requirements Management  

In this article series, I am outlining 42 questions that a product manager should ensure are answered across the following SDLC phases:

• Product Strategy – The reason a product exists, and its intended goals.
• Product Roadmapping – The broad timeline in which future product capabilities are slated for release.
• Initiative Planning – The definition of a project to deliver capabilities within a budget and schedule timeline.
• Solution Design – The people, process, systems and policy designs required to deliver the required capabilities.
• Solution Development – The people, process, systems, and policy capabilities have been developed and are ready for testing, training, and deployment planning.
• Solution Readiness – All solution aspects are accepted and ready to be deployed.

In the previous article, I focused on seven product manager’s accountabilities when designing a solution. This article focuses on seven questions to be asked when developing a solution.

1. Has there been a line-by-line confirmation that each in-scope requirement has been included in the developed solution? Some can argue that the line-by-line requirement confirmation occurs during testing of the solution. That, in and of itself is true.

But it's also true that the longer in the development cycle you wait to find problems, the more expensive and …

Please log in or sign up below to read the rest of the article.