Scaled Agile Framework & Agile Development 2.0

[BlairRM]

Hi All,

Recently moved into the ServiceNow world and need some help:

When looking at the Agile Development 2.0 plugin and the Scaled Agile Framework, is it best to use these in partnership with one another or are you best to only use one or the other? Any opinions on which plugin is best for which activity would be greatly appreciated. 

Many thanks, 

Blair 

[Chalan B L · Accepted solution]

Hello Blair,

Go through these two blogs and i hope you will get answer..!!!

Why SAFE? if you need to scale your development efforts on a larger scale—larger products, more teams, and longer timeframes—while stilll applying lean and agile practices? That's where the Scaled Agile Framework, or SAFe, comes in. 

Why Agile? Agile software development is a flexible approach where user requirements evolve into software solutions through an iterative collaboration between the developer and the users working together in tightly knit teams. This approach is implemented in a framework called Scrum, which lays out the roles of the development personnel and their activities.

SAFe 101—What is the Scaled Agile Framework and why do you need it?

Agile 101—What is Agile development and why do you need it?

Mark correct and helpful if it helped you..!!!

Regards,

Chalan

[BlairRM]

Hi Chalan, 

Two great links, really appreciate it!

Blair 

[David Wells_ SP]

The teams I'm coaching I advise in this way:

- If your problem involves a single team developing one or more products, Agile 2.0 best fits this need IMPO.  It has all the tools needed to manage themes, epics, stories, tasks, and sprints to support an individual team's work.  Agile 2.0 has certain advantages in that it's been around longer and is (for the moment) a more mature product.

- If your problem involves multiple teams working together on common goals - even if they are not practicing Scaled Agile per se - the SAFe product offers unique capabilities to support this.  Among those are the ability to plan at a higher level than stories across sprints, the ability to create, plan and manage roadmaps of features across multiple teams and sprints, a larger timebox (called Program Increments in the SAFe lexicon) with which to plan and track feature delivery, and the ability to track and visualize dependencies across teams and sprints.  I have several teams who are using the SAFe product with good effect, even though they are not quite large enough to constitute an Agile Release Train per SAFe guidelines.

Happy to discuss further if you'd like...

David

[Ben Wilson2]

What annoys me with SAFe is that it does not appear to tie into the other parts of SN like Agile 2.0 does.