Hi, my name is Frank Schophuizen and I am working as a consultant in SAFe (Scaled Agile), CM (Configuration Management) and ALM (Application Lifecycle Management) for TOPIC Embedded Systems.
I have over 30 years experience in ...
Top Posts & Pages
Category Archives: agile
Introduction SAFe 4.0 states that an Agile Release Train consists of 50 to 125 people. Larger teams should be split up in multiple release trains and smaller teams should be organized as individual agile teams, not as an agile release … Continue reading
One of the most difficult things in change management is change people’s habits. Habits are like reflexes: act without thinking why and how to do it. Habits save a lot of time and energy. How difficult would walking or driving … Continue reading
When SAFe 4.0 was release was my first question: which one is better, 3.0 or 4.0. In my opinion the 3-level model of SAFe 4.0 is definitely an improvement compared to SAFe 3.0. The triangle RTE – System Architect – … Continue reading
In part 2 we have looked at estimating and planning of a release of the Agile Release Train. This is mainly on SAFe portfolio and program level. In this part, I will focus more on the challenges of estimating and … Continue reading
This is part 2 about implementing SAFe with Jira. In part 1 I explained how we implemented the portfolio, program and team backlogs as the 3-layered structure of SAFe in Jira. You may recall that we renamed them to business, … Continue reading
In this article I am not going to explain what the Scale Agile Framework (SAFe) is and what Jira is. I assume you know, and if you need more information go to http://www.scaledagileframework.com and http://www.atlassian.com. But before we start, there … Continue reading
The simple answer is: Yes, configuration managers are going to disappear! The more comprehensive answer to this question is that configuration management is not going to disappear, but the configuration manager will be. We can compare it to the change … Continue reading