A lot of our clients are technology vendors that struggle to use the SAFe Operational Value Streams “out of the box”. Here, I explore how such a B2B vendor should organize around value when building products that are used to support its customer’s business operations.
Agile Marketing Resources
Agile Marketing helps marketing organizations become faster, more flexible/responsive, and more collaborative in order to be better tuned to the business they’re supporting.
Inspired by the more general Agile approach, Agile Marketing describes a mindset of continuous learning and validation, customer-focused collaboration across functional silos, adaptive and iterative campaigns, and more responsive/continuous planning – all as a way to deal more effectively with uncertainty and complexity.
Agile Marketing teams use techniques such as Scrum to work in an iterative cadence and Kanban to visualize and improve the flow of work. Larger marketing organizations use approaches such as SAFe (Scaled Agile Framework) to align and collaborate across teams of agile teams.
Hybrid work best practices by Sagi Smolarski & Yael Rabinovitz, AgileSparks, with guest writer Yael Goldberg Katz from AT&T As a side effect of the
Could the INVEST criteria Bill Wake came up with for evaluating User Stories help us come up with effective PI Objectives in SAFe as well?
I think a good PI Objective should be:
– Independent – meaning ideally it could be delivered and evaluated on its own without any dependency on other PI Objectives. And if a team is able to own a PI Objective and delivery it on its own – it’s a sign that it’s a cross-functional autonomous team.
Here’s a frequently asked question in the SAFe community: I wanted to understand what SAFe says about someone who wants to go faster than 2 weeks of iteration? I mean the whole PI concept is based on 5 iterations worth of planning. What if a team/organization wants to develop and synchronize faster than 2 weeks? Is speed going to be compromised by following the standards of PI cadence?
Here’s my take:
Adjusting Cadence Length in SAFe – Can you? Should you?
How do we handle Scope Changes in a SAFe Program Increment?
A question about handling scope changes in SAFe was posed recently on a forum I’m participating in (The SAFe Community Forum). This is a question posed regularly in training and on ARTs I’m coaching so I thought I’d provide my thoughts here.
I’m encountering more and more people that are trying to solve different kinds of problems with Scrum:
People designing Consumer Goods
Accounting professionals focused on Revenue Accounting
Marketers of many kinds
Healthcare professionals.
I’ve been having some interesting discussions with them that I thought I might share.
As a coach helping organizations become agile, I’m asked how to change the mindset of the people, how to help them see things in a
“Oh no, it’s the retrospective time!”
This cry for help is not uncommon, I’m afraid, among practitioners of Scrum. That is a shame. For me, this meeting is the climax of the scrum framework – this is the place where we get better. The discussions can get very deep and very meaningful. I would like to show here how to move from the statement appearing in the title of this paragraph to “Oh boy, it’s the retrospective time!”.
In recent years I’ve been working with many software development teams and almost all of them struggle with estimating the work. The energy spent on
Request for additional information and prices
