Home | Workflow Alignment | Workforce Empowerment | SimOps | About
Products and services delivered to the customers are typically a combination of integrated systems which, on their own, are often integrated systems by themselves.
Here are a few aspects to take into account in order to streamline the process:
Teams are ideally in a position to accept the items they are asked to deliver on, have the freedom to decide on the design of the implementation and have access to an environment with which they can proof by themselves they meet all acceptance criteria associated with the requirements they received.
To achieve this, the workflow alignment between the teams in the context of the entire solution needs to be carefully considered and optimized.
<aside> 💡 Let us help your organization reach its full potential
Send me an email 📩
</aside>
The following metrics are a snapshot of the possibilities. Alottabits has the experience to develop tailor made insights for each organization to align with the specific business needs at the time.
While they are shown as static images, an actual implementation provides access to these metrics through an interactive interface, drawing on a full process data set, allowing for deep data-mining and root cause analysis.
Flow Metrics are great tools to investigate the complete delivery flow throughout the organization and at each integration layer.
Flow Time and Flow Efficiency are great top level indicators:
Here is an example of what Flow Efficiency graph would look like:
The boundaries are based on the statistics of the Stories completed during a 5 Sprint window
In the above example the efficiency increases, which is good, but one would seek to narrow the band and look for ways to improve more rapidly through further investigation.
Value Realized is another great way to investigate the efficiency of the organization and allows as well a deep dive into the details of individual teams and the interaction between teams.
Here’s an example of what a chart would look like to represent the value delivered at different integration levels:
In this example, stories are integrated into features, which are integrated into epics.
The data-mining interface allows for a drill down to team level and sprint to investigate the process.
If the test coverage is sufficient, trends on bugs are a good indicator of the maturity of the system under development.
Not all bugs represent an equal amount of risk to the program. Characterizing bugs based on their severity and the maturity of their solution offers a great leading indicator.
Here’s one example of what that could look like as a trend:
When new functionality is added to the system, it is natural to see an increase in bugs. If there is sufficient test coverage and resources to address the bugs, the Maturity Index typically shows a straight line down, after a peak. A great leading indicator to assure on time delivery at the needed quality level.
RJ Visser
m: +31 6 2708 2110
