The Scaled Agile Framework Explained With Video's Collection

Too big to be true? Nothing's Impossible.

Are you releasing into production every two weeks, but need to build a feature that's going to take Four months to complete?  How can you do it? Either using grooming methods or Continuous Integration to keep everyone working, or user stories brackdown , or testing? How?

SAFe Foundations

SAFe provides the basis for building a truly lean and agile software delivery organization.

In this Roojom I will present  a collection of an introduction items to the Scaled Agile Framework (SAFe) Foundations and how it can help successfully scale lean and agile practices across teams, programs and portfolios to optimize value flow.

Portfolio Management With SAFe

“Program Portfolio Management represents the authority for oversight of strategy and investment funding, program management, and governance for a specific portfolio of programs in the enterprise. SAFe prescribes a number of transformational patterns which empower teams and programs, decentralizes decision making and speeds time to market, thereby helping deliver the business benefits of an always improving, Lean|Agile software enterprise.” In this Roojoom you may find a review over the various elements of SAFe portfolio including lectures and tools implementation.

SAFe HIP -Hardening | Innovation | Planning Abstract

HIP sprints provide cadence-based opportunities for Hardening | Innovation| and PSI/Release Planning. is whatever you need to do to Make the System Ready for Production. 

 On one hand we may hear that Hardening is very important, and absolutely needs to be called out explicitly, otherwise there is absolutely no chance to reduce it or even get rid of it in the future. On the other hand , it sounds overly waterfall’ish, representing an additional phase in the process. So lets review what is HIP , how its done and what others and SAFE people think about it.

The Deployment Production Line - Continuous Deployment

Agile introduces the idea that the team should get their software ready for release throughout development. The principles and methods of Continuous Delivery are rapidly gaining recognition as a successful strategy for true business agility. Small changes are constantly tested and that are deployed and released to Production immediately upon verification.  What is it really? How is it Done? What its relation to DevOps ? and some examples.. Here it is :

It’s Show-Time! The Show and Tell Meeting

This is a key meeting. The purpose of this session is for the development team to present back to the customer or product owner what it is that they have delivered during the previous sprint. its about standing to our commitments and present them, Its also about feedback and its also the principle of demonstration. When we can actually see and experience something, it becomes real to us. And its also a great opportunity for the team to pat yourselves on the back and brag a little. Here’s some more tips on how to get this one done.

SAFe Release Planning

In large scale agile development projects, product backlog management and release planning are crucial activities to enable successful deliveries.The larger the project, the more important it is to perform look-ahead planning. SAFe recognize the importance of release planning. Her's how its done.