agile_problems

I got the opportunity to temporarily experience working as a RTE. I will document my experiences here.

Enthusiasm is the only part of the growth indicator Engagement.
It checks how everyone is doing at the end of a PI.
We have chosen a scale with a couple of questions and present the results anonymously.

The last growth indicator in the Agile Performance Report is Engagement.
Our department has chosen to rate the enthusiasm of everyone in the ART every Inspect and Adapt.

Fifth part of Productivity is Planning Accuracy.
In a PI the average percentage of delivered story points of all teams and every sprint.

Fourth part of Productivity is Train Program Velocity.
In a PI the sum of effort of the features divided by sprints gives a measure to what the train program velocity of an agile release train is.

Second part of Productivity is Business Value.
In a PI the sum of the business value of the features divided by the sprints gives a measure how much value the agile release train delivers.

First part of Productivity is the Program Predictability Measure of a PI.

Productivity is determined by the Features that are delivered in the PI by the ART. These numbers can be used by a releasetrain engineer to monitor how far the ART is with achieving their goals.

Fourth part of Time-to-market is Deploys and/or Releases.
This part can indicate how much the ART support continuous integration and deployments and shorten the time-to-market.

Third part of Time-to-market is Throughput.
This can be used by the releasetrain engineer as a guide how many features per PI their releasetrain can handle. Almost like how the scrum master can use a teams velocity.

Second part of Time-to-market is the cycle time of a feature.
How long does take for a known feature to be analyzed and rolled out to production?

After this meeting I planned some follow-up calls to be more aligned in our agile releasetrain.

I’m creating an Agile Performance Dashboard for our ART.

This is a time consuming feature, because being compliant is not thoroughly defined.
It may be because of the size of the company that these refinements also take so long.
@ Rotterdam, Netherlands

I like to refresh my knowledge every so often. And with the new SAFe version and me deciding what career path is. It’s interesting to see if there will be other take aways than before.
Anyone else did this training?

Sometimes it’s difficult to determine if an opportunity is timed correctly.
Right now I want to expand my skillset as a scrummaster first.
Before I truly transition to the role of a releasetrain engineer.

Exactly...mccutcheon with
・・・

I haven’t been posting of late. But work has been good even though I have been working from home for almost a year now. I have decided to stop being a Product Owner and fully focus on my Scrummaster role. I will be posting more from this perspective.

Thank you for following .

If you’d like to share your then you can DM me.

We work with multiple teams so there is always a risk that things are build not as design. The hope is no bugs are found when integrating bit it shouldn’t be a surprise. Review what went wrong and make an agreement how you can avoid it in the future.

This was truly a communication problem where the business assumed and the previous product owner wasn’t clear enough towards the business.

Just made a new page for agile_problems.