We are entering into a new organiation where all should go agile and embrace the SAFE model. I have just taken SAFE training and is among seen as a old waterfaller :) I'd like input on a transformation like this and if there is a line in your opinion where agile projects simply will not do the trick to 100%. I am working with infrastrucure, building new data centers, building new office sites etc. For me this is a challange with 6 week sprints that does not even cover a order of HW. I just read this article: https://www.pmi.org/learning/library/pm-ro...ile-world-9350.
What is your thoughts? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I am one of the key persons to implement SAFe in my actual work place. I have expertisse in Agile that was born outside the software domain. SAFe is the most anti-agile framework you can see. I have exposed that in my actual work place (and the reasons why) but top management took other decision. In my personal opinion organizations are taking SAFe becuase few changes are needed to use the actual processess BUT it does not mean that thanks to use SAFe they will implement Agile and gaining in agility. They buy the "silver bullet". So, my recommendation is relax and try to understand the whole frmawork mainly read and understand Scrum (Scrum is the Scrum Guide, other things are just implementations of Scrum using specific tools like user stories, kanban boards, etc) and real and understand Lean and Kanban (the first is not a method. Is a whole phylosophy. The second is more than a tool, is a method). Saving Changes...
I recently transitioned to a SAFe project from waterfall as well. Think of the Epics, Features, Stories and a different way to break down what you already know as the WBS. Epics and Features might be your previous level 1, 2 or 3 for a complex project, and the stories would be those items further decomposed. SAFe and Agile still allow for dependencies (build the floor before the walls), but allow you to prioritize according to your needs (maybe this "sprint" there needs to be a better safety audit).
You also don't need to do Sprints at all - use Kanban or Scrumban with a Work In Progress focus.
