Enterprise Scrum Development Process Flow
Glen Alleman MSSM
Vietnam Veteran, Applying Systems Engineering Principles, Processes & Practices to Increase the Probability of Program Success for Complex Systems in Aerospace & Defense, Enterprise IT, and Process and Safety Industries
Here's how we write software for a not to exceed budget, on a deadline, with a mandatory set of Capabilities and Features that implement the Capabilities needed to accomplish the Mission and fulfill the Strategy in a State Public Insurance domain. The needed Capabilities, Features, and Stories, must Go Live in the first week of October every year.
This process flow has been applied in a wide range of technical and business domains beyond the ACA domain. From?enterprise?IT to manned space flight avionics?systems.
In all these domains, there are some core assumptions:
— We know what?Done?looks like in some form. Usually,?a minimum set of Capabilities is needed to accomplish the business and technical?mission in units of measure meaningful to the decision-makers, starting with Measures of Effectiveness and Measures of Performance.
If you don't know what?Done?looks like in a unit of measure meaningful to the decision makers, you're?on a Death March project, from Death March, 2nd Edition, Edward Yourdon.
—The myth that it's in doing the work we discover the work is just that, a Myth.
— The development and even the emergence of?Capabilities?are held in the Product Roadmap. It's from this Roadmap that Features emerge.
If you have no needed Capabilities, then you can?go live?every time you have working software. But that usually means you have a de minimus application, where no one?really cares what you are producing as long as it's something.
—That Product Roadmap has a?Release Plan?showing what Capabilities are needed in what order to meet the business needs of those paying for your work.?
—The System Integration and User Acceptance testing can be done with Kanban in this paradigm.
Here are the details of the steps in the first picture:
领英推荐
Estimating in this Process?Paradigm
The challenge?for all agile development?is estimating the work when there is a deadline and a budget to stay inside of.
The first step is to have some means for creating a?Reference Class?that can be used to size the highest level of the work. This usually means having someone or access to someone?who has done the type of work before.??
When I hear?we've never done this before, so we can't size the work. The answer to that is simple:?
In our current domain, the estimating process works like this
References for Integrating Agile Development with Program Planning and Controls
No matter the domain, the context, the development processes, or the project management processes, there are Five Immutable principles of project success.
The basis of success for all projects, no matter the domain, project management process (Agile or Traditional), project management tools, and technology, starts by answering the questions posed by the Five Immutable Principles, published in?Performance-Based Project Management, American Management Association, February 2014.
Guidance on Managing Agile Projects
More Resources for Increasing the Probability of Project Success
A collection of conference presentations, white papers, book chapters, and journal articles on managing projects and programs in a variety of domains, where arriving on or before the needed time, at or below the needed cost, with the needed Capabilities to accomplish a mission or fulfill a strategy is necessary for the success of the project.
Project Manager
2 年This process flow is a great example of how Kanban supports and complements Scrum. In the end, "the Scrum framework is purposefully incomplete and only defines the parts required to implement Scrum theory."