I am teaching Leading SAFe with my co-instructor Jose (Joe) LaTorre USMC (Ret.) this Friday! The kit is prepared! We have some prep work to do still but I am SUPER EXCITED about teaching the course! Thanks to the Scaled Agile, Inc. folks for the support and to my gracious and eager to learn clients at ESC!
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 planning on program and team level. Since Jira does not offer much cross-project support, we will be using the structure plugin. So first, we must get our structure boards right.
Structure plugin (revisited)
Last time, I explained that you can make a structure board with the structure plugin, and populate and locate issues on the structure board with synchronizers, in particular:
- Filter synchronizer – use a filter query
- Agile synchronizer (JIRA Agile (Greenhopper) – using Epic links and Subtasks
- Links synchronizer (Issue Links synchronizer) – using “Implement” links
The filter synchronizer can be configured to remove issues that are outside the filter query results. For example, if you filter on
View original post 1,538 more words
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, system and product levels. In part 2 we will dig more deeply in connecting the layers.
Since Jira (core) is not able to visualize linked relationships, we use the Structure plugin from ALMworks. On a structure board, you can add Jira issues, you can sort them and put them in a hierarchy (i.e. an issue nested under its parent issue), manually by drag-and-drop or automatically by synchronizers. A synchronizer interprets the data in Jira (e.g. a filter, Epic link or issue links) and puts the issues in the structure at the right place. Synchronizers work bi-directional. For example, by adding or removing a link the synchronizer…
View original post 1,168 more words
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 are a few things that are important to know:
- Jira is not designed for agile development. In essence it is an issue tracking tool. You need plugins to added support for Scrum/Kanban. Currently, there is no plugin for SAFe support.
- SAFe is not a prescriptive process model. It is a framework. You can implement it anyway you like, leaving out what does not work for you and adding thing that you need.
My experience with SAFe and Jira is based on the implementation of SAFe (with Jira) with a customer I worked with in a development and innovation organization of a large, multinational technology company for commercial products for consumer…
View original post 1,048 more words
Updates to the Scrum Guide – The 5 Scrum values take center stage – Scrum.org Community Blog
We are celebrating our Independence Day in the USA! The fight against tyranny is a part of our history. This nation was built on freedom and sacrifice. A nation of liberty earned with great sacrifices from our men and women. A nation of people who loved and feared God, and are loved by God. Thank you to all those whom have (and will) served our country in uniform. Their efforts enable us the freedom from which we can conduct business!
There was an update on the SAFe on June 23, 2016 where the good folks at Scaled Agile released a simplified version of the SAFe Big Picture. This new tool will make it easier to introduce the Scaled Agile Framework for the Enterprise to folks whom are not familiar with it. Continue reading