![]() ![]() From the 5 week iteration of the PI, the last and the 5th iteration is called IP(Innovation and Planning Iteration: Innovation part is the creative time for the team- shipping days or hackathons.When the train is running together, the architecture and infrastructure is taken care of, and this is done by the trained system architect called the architectural runway so the train can run smoothly and as fast as they can.At the end of the PI, a System demo is carried out with the whole train together which is the demo of the integrated system.Bi-weekly meetings are held with team scrum masters and RTE.The Program level SAFe provides visibility and objectives of the program.The Product Owner, Program Manager, RTE and the ART teams work towards the objectives they can achieve and identify risks, dependencies on the train.Governed by RTE acts as a trained scrum master(program manager of the program level).The content is decided by the program manager/product manager: Program backlog as features.The team commits to the PI providing visibility to the business on the objectives of the PI.Each PI starts with planning- vision, and roadmap of the train features for the next PI. Just like Scrum is, the program level SAFe framework also is a Timeboxed effort and this is called a PI(Program Increment).This team of teams is called ART(Agile Release Train). ![]() A Larger team of multiple scrum teams work together to deliver a larger system.If you are a Portfolio/Program/Project Manager in the waterfall model, that have worked on business plan, project charter and under a PMO that has governance process across Portfolio/Program and Project Management, tying these areas together so it aligns with the overarching business strategic initiatives, you can easily connect SAFe Agile in a similar fashion(and we have already learned that this is for large, complex initiatives). SAFe looks at aligning with the strategic and business value of the organization. The iteration starts with planning meeting which discusses the user stories that they can deliver by the end of the iteration/sprint and after each iteration, they demo and get together for retrospection to improve for the upcoming sprints, in the guidance of the scrum master. If you like to read further on this framework, refer here. And you would have the agile ceremonies like Daily Scrum, Sprint Planning, Retrospection, Demo etc. You would have a Product Owner, Scrum Master and the team working towards a sprint goal and in iterations of two weeks each. TEAM LevelĪt the TEAM level, it is pretty much the same as an Agile Scrum Framework. Let’s look at each level in detail for deeper understanding and it’s easier when we discuss from the bottom – top. And this is for relatively smaller teams of 100 or less and requires less collaboration. SAFe 3.0 has Portfolio, Program and Team levels. And this is for larger teams that require hundreds of people to develop and deploy products and solutions. SAFe 4.0 has Portfolio, Value Stream, Project, and Team levels. SAFe has two different levels of implementations, one is SAFe 4.0 and the other is SAFe 3.0. Think of SAFe as an agile and lean methodology for large and complex portfolio, programs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |