Have all been useful tactics when I’ve scaled Scrum. High-level qualification of Epics for Business level and Architectural level soundness by leveraging early “Grooming” activity.Using x-team Sprint Reviews as a synch point with leadership and stakeholders.I also liked the fact that they spoke about inputs from: the program, the team, and other stakeholders. I’ve been talking about this as part of solid Backlog Management for the better part of 10 years. Capacity allocation within the backlogs was mentioned at both the Program and Team levels.Whole-team commitment to Release Plans, including “negotiation & acceptance” with leadership.With a strong emphasis on high-level Visioning, Road-mapping, and Strategy. Leveraging Release Planning as a central activity to gain x-team collaboration.Integrating cross-cutting groups like architecture, UX, and DevOps in the PSI Planning and Release Train execution.Actively spiking work within sprints emphasizing architectural and design look ahead.Now I haven’t made innovation & planning a direct part of the hardening sprint, but the activities between ART’s have been the same. HIP Sprint (Hardening, Innovation, and Planning) as a transition from one ART to the next.It simply works better, particularly from a dependency & integration perspective. For a long time I’ve been a proponent of synchronized work at-scale. Synchronized sprints across all teams within the ART.SAFe seems to be more prescriptive than I’ve been in the number of recommended sprints, but the intent is the same. Agile Release Training (ART) with a fixed number of 2-week iterations.This also includes Continuous Integration and Automated Testing. Notion of Scrum + XP practices for team level execution with a strong focus on technical practices and the craft in software development.Here’s a list of the things that I like and have used: I not only agree with it, but I’ve been using them at-scale for many years. Before SAFe, Agile at ScaleĪs I said earlier, there is quite a bit of SAFe that I agree with. And of course, here’s a link to the “big picture”. If you don’t have a clue about what SAFe is, then this 1-hour overview might be helpful to you. In the remainder of this article I’ll explore my learning’s, reactions, and concerns about SAFe. I guess my point is-I wanted to give it a chance. I wanted to listen, learn, clarify, and fully engage the class. I shared most of my concerns in this blog post.īut beyond all of the reservations and assumptions, I tried very hard to go into the class with an open mind. However, I did see some patterns in the implementations. These teams were part of larger scale adoptions, which are difficult to orchestrate with or without SAFe. I’ve also coached some teams who had/have adopted it in some form our fashion. I’ve seen Dean Leffingwell provide various overviews both in video and in person. I’ve done quite a bit of research on SAFe. I was certainly apprehensive going into the class. Consider it part a review of the class itself, but also providing some general feedback on the framework. In the remainder of this piece, I want to explore my SAFe discoveries in more detail. So from that point-of-view, I guess I’ve been an early adopter of SAFe. And I’ve always coached Scrum teams to leverage Extreme Programming technical practices.Īll of these approaches are in many ways a part of SAFe. The foundation of all of my program level Scrum of Scrums execution has been Release Planning, which I described well in this article. For portfolio planning, budgeting and forecasting I’ve leveraged an extension called the S3 or Scrum of Scrums of Scrums that I saw implemented in 2007. But I’ve couched those techniques under Scrum of Scrums for agile scaling-and with fairly good success.įor example, I’ve been leveraging synchronized Agile Release Trains and Hardening Sprints for years and years. You see much of what I learned in the class I’ve been using and doing for a long time in my own agile journey. It’s more so that I’m having a challenge fitting them into my own experience in a useful way. It’s not that I’m having trouble with the concepts or approaches. This enables me to teach several SAFe courses, to kick-off and coach Agile Release Trains (PSI’s), and to generally coach organizations that are adopting SAFe.īut to be honest, I’m still digesting SAFe. A few days after the class, I received an email telling me I passed the exam. A few weeks age I attended a 4-day Scaled Agile Framework class with a result of sitting for my SAFe Program Consultant (SPC) test.
0 Comments
Leave a Reply. |