Product Backlog Template: Deep dive on reasoning and regulations (6..11)

<< Previous section - Testing notes

THINGS TO KNOW (continued...)

Other:

The lack of knowledge, centralization, consistency, respect to compliance and regulations, ignorance of existing and upcoming deployments, and unknown overall product capabilities leads to:

• Frustration;

• Perception/impression of an immature company;

• Waste in time spent in meetings;

• Waste in effort gathering an inventory of current state;

• Sprawl of unnecessary tools incurring all of the above bullet points;

• Time in maintaining and troubleshooting bespoke applications and current implementation;

• Risk to any efforts toward compliance going forward and already achieved;

• Increased time and investment for any onboarding of employees;

• Waste in time for onboarding and training of delivery/installation teams;

• Increased time and investment for onboarding of any new developers;

• Security risk to our customers;

• Inability to predict time-to-market or trial-type offerings;

• Inability to scale; and

• Inability to integrate within the company and beyond.

NOTE: In the discussion of merely addressing the issue around two failed transactions in the Azure Marketplace, and one successful transaction that was subsequently unable to be located to assure the actual funds were received, a total of 9+ hours of meetings, including 5+ individual stakeholders each, were held to discuss the issue. None encapsulated the full scope of the multiple problems but in actual funds were received, a total of 9+ hours of meetings, including 5+ individual stakeholders each, were held to discuss the issue. None encapsulated the full scope of the multiple problems but in itself were fairly expensive. (Yes, I did the math.)

Reasoning: "Catch all" for anything not previously is not covered. The effort is to have the backlog allow for anyone to groom, task out, and begin work comfortably.

Regulatory guidance: TODO

Next section - Summary >>