![]() Regardless of the tools you use, visualizing the entire program board becomes much easier when all the issues are already in Jira. Or if you’ve made changes to how you store PI information that are incompatible with Easy Agile’s Programs, you could opt for a read-only version of the program board that allows everyone to track it through the Smartdraw Visualscript PI board. You can use Easy Agile’s Programs to facilitate your PI planning sessions and drive your transition to a distributed, paperless PI planning session. But with the right tools, Jira can be just as useful for visualizing projects. Of course, butcher paper and sticky notes do provide a level of visualization not easily replicated in Jira alone. This isn’t to say that Post-it notes can’t be helpful when you are breaking features down into stories.* (Note: We use the epic-feature-story hierarchy here for consistency with the SAFe literature) However, creating these issues in Jira will allow you to directly create dependencies and link to other tickets as you’re considering them - not as someone is trying to painstakingly transcribe the RTE’s scrawled notes. When a PI planning session includes the tools each team uses on a daily basis, you will see teams work more freely in the team breakout sessions. Where will the artifact live? Who will have access to it? Posting the butcher paper outside the release train engineer’s (RTE) office is great for the RTE, but not for everyone else stuck with a low-resolution digital photo.īut perhaps the biggest drawback to all this is that despite how or where you hold the meeting, how you take notes or where you store those notes, all that information has to end up on your planning platform - and for the majority of us who are using Jira, all those steps could have been done just as effectively (and a lot more simply) using the tools readily available there. Transcribing notes to digital format increases the chances of human error.įinally, while the existence of a single artifact that everyone can reference for dependencies and prioritized issues is great in a big-room planning session, the benefit falls apart as soon as that meeting is over. Paper is easily lost (and those sticky notes never stick as well as you want them to). For any team that relies heavily on technology (read: all teams!) planning every task for the next quarter with butcher paper, Post-it notes and string is both frustratingly simplistic and impractical. Let’s face it: Typical planning strategies have some flawsįor distributed teams, flying everyone to the same place presents a large logistical and financial challenge. ![]() Unfortunately, following a strict SAFe-prescribed quarterly cadence for these sessions has several drawbacks. ![]() This big-room planning session was originally designed to get everyone in the same space to hold all the important planning conversations, so teams can quickly discover dependencies, priorities and (over)allocations. Skip the paper and highlighters to work more efficientlyįor many Agile teams, one of the biggest challenges to implementing the Scaled Agile Framework (SAFe) is the inclusion of the Program Increment (PI) planning session. Here's why you should switch to planning within Jira instead. Traditional PI planning relies on old-fashioned in-person meetings with butcher paper and sticky notes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |