The classic for loop is a widely used feature of javascript programs. It can be used for running any piece of code multiple times, and it used to be what was used for implementing operations on arrays.
Let’s say we want to improve quality. We decide to use the Scrum framework. The scrum framework talks about sprints, sprint goals, daily scrum, and many other things, yet it doesn’t directly discuss quality. There is a leap of faith here: we believe that if we will use the scrum framework, quality will improve.
At AgileSparks, we’re known for speaking out against what we call Agile Theatre where a company goes through the motions of adopting Agile but stops short when it comes to changing the way the business operates. Real agility affects every aspect of an organization and therefore, requires a massive cultural and operational shift.
SAFe is a path to agility, but the organization does the heavy lifting
Introduction
As a system admin or a project manager you often find yourself torn between management requirements and users who find the tools not as comfortable as they would like them to be. Jira is without a doubt a tool that can raise mixed emotions among users. Lucky for you, most of the users’ challenges can be easily handled.
In the last couple of years, I’ve been writing about SAFe on the AgileSparks Blog, providing guidance articles for the SAI, and creating some complementary approaches and services in the SAFe context. All are based on experiences in the trenches helping AgileSparks clients achieve agility at scale. I recently completed a curated collection of some of my favorites and started to provide copies of this book to participants of my Implementing SAFe and RTE classes.
The Scrum Master’s role has become one of the most important and challenging roles in modern organizations since they act as the main interface between top management and the teams that actually produce and deliver the company’s value to the customer.
Recently, I had the opportunity to work on legacy code with several teams from various organizations. I would like to share my experience.
We usually start by choosing a piece of code that is “painful”: changing frequently and “scary” to touch because of its complexity. We explain that our purpose is to make the code simpler, readable, and easy to change. Establishing the motivation for what we do is important!
Seriously, please don’t come.
Don’t come if you’re looking at it as a formality since you already know everything about agile and just need the SPC (SAFe Program Consultant) Certificate.
Don’t come if you’re looking for the cheapest way to get your SPC so that you can add it to your resume.
Don’t come if you don’t know anything about agile and believe the SPC is your silver bullet to becoming an agile coach at the enterprise level.
Don’t come if you’re looking for the certificate rubber stamp.
Marketing Backlogs in the Trenches
Last week I facilitated a 2-day Agile Marketing workshop for one of my clients. As usual, the discussion about the Marketing Backlog and how to move from a big-bang marketing campaign to a more iterative approach via smaller slices of stories was one of the highlights.
As usual, I introduce the concept of User Stories which are the most popular way to represent Product Backlog Items (PBIs) in the Agile world and are also very popular in the Agile Marketing space. We looked at some awful examples of stories, such as “As a marketer, I want to install Drift on my site” or “As a user, I want to see a webinar” and then moved to stories that provide more insights about a real user (e.g. “As a VP Marketing focused on Demand Generation”) and their intent (e.g. “so that I could get more demand generated from people who hate forms and lead magnet registration-walls”)
We then broke out into multiple teams each taking an actual campaign/project they’re planning for 2019 and creating the Marketing Backlog for it.
What is the connection between Uncertainty and the Scaled Agile Framework?
Uncertainty is one of the core reasons we need to be agile. Different modes of Business/Requirements/Technology uncertainties impact our economic costs in product development – especially the potential impact of risk. The first principle of SAFe™ is “Take an economic view”. I frequently use my “uncertainty filter glasses” to take an alternative economic view. I find it helps Scaled Agile/SAFe™ practitioners/leaders understand both the need for Agility as well as examine various work system design considerations. In this article, I introduce the Stacey Matrix which is one of my favorite models for understanding the uncertainty landscape as well as the implications of uncertainty on various specific SAFe™ design decisions.
Request for additional information and prices