A lot of people talk about scaling Agile. It’s all the rage nowadays. Everyone wants to scale Agile. But what does that actually mean? What does it imply? What are the underlying assumptions?

When Scrum is introduced in a company, most of the time, the development team embraces it with lots of enthusiasm.

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context.

The subject of this blog post might seem unusual. But having worked with multiple development teams, I've gained some experience with team members having (symptoms) of Asperger's. I mostly contributed to the team as a Scrum Master or Agile Coach.

Before I begin, I have to make sure you’re not fixed on a misconception. The Daily Scrum is not a status meeting, nor a report back to the team. It’s a planning event.

In this blog, an overview of the professional QA as a quality coach for a cross-functional team is discussed.

When do you use Nexus?

The story of the Wygat Weed Whacker goes back many years – to the time we bought our first home in the beautiful town of Allen, TX.

 

A lack of defined engineering practices, standards and tooling is an often observed problem in software development, regardless of whether Scrum is used.

 

This blog post is about a little box. A little transparent box. The box contained only one sticky note. A sticky note with a milestone.

Although the Daily Scrum seems to be a simple and straightforward event, I still encounter a lot of teams struggling with it. In this blog post, I'll share my tips & tactics.

Update: after receiving some valuable feedback, I've added the third lesson learned. 

Have you ever seen a Sprint Backlog that can be reused across Sprints? I have!

The concept of user stories is a well-known tool for describing requirements. In a simple format, it captures the ‘who’, ‘what’ and ‘why’ of a requirement.

GREAT DALLAS ICE STORM OF 2013  

This blog is the sequel to my earlier blog - Ent

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.

WALT'S CHALLENGE   

The Scrum Guide begins the description of the role of the Product Owner as follows:

There’s an old Wayne Gretzky quote that I love...

A pair of recent findings from the Standish Group confirm the astonishing success and cost savings of Agile approaches over waterfall.

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.

This is the final post in a three part series. Please like, share,and/or comment.

This is the second post in a three part series. Please like, share and commentand I’ll be sure to update you when the next post in the series comes out.

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.

Through my years of trial and error,  I have learned there is no one size fits all solution to transitioning organizations to agile...context is king!

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.

VersionOne does an annual "State of Agile Development" survey and publishes the results for the cost of your email address.  Thanks VersionOne!

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context.

If you have seen the TV documentary series Hoarders which depicted the real-life struggles of people who suffer from compulsive hoarding. Some victims suffered so severely that they were often drowning within their own filth.

The Scrum Guide requires that the Product Owner ensure that "key stakeholders" attend the Scrum Sprint Review, but who are these "key stakeholders"?

Is there a way to help organizations move from a Change Transformations mindset to a Continuous Change mind set?

In Jeff Haden's recent post entitled "The One Attitude Every Successful Person Has", I was struck at how aligned this attitude is with the Agile Mindset. What do you think?

Father's Day offered an annual moment for me to reflect on the journey of a humble and influential man whose life was tragically cut short in 2002 - my Dad. Although it has been a number of years since his passing, he contin

Recently discussing design and programming with an external programmer, he explained me his approach of defensive programming. But before going in detail of his explanations, Wikipedia help us to define the defensive programming:

The Scrum Master role can easily be misunderstood as it is harder to grasp by reading the theory; hence people often compare the Scrum Master role to Project Manager or Technical Leader. Scrum Master's primary job is to place himself in service consciously, with self-awareness, and for the benefit of his customers.

I was recently contacted by a senior executive of a mid-sized company that is evolving their product development to Scrum. He explained a situation he had been in and wanted my opinion.

Scaled Professional Scrum is based on unit of development called a Nexus. The Nexus consists of up to 10 Scrum teams, the number depending on how well the code and design are structured, the domains understood, and the people organized.

Scrum brings agility to and creates Agile organizations through the implementation of empirical process control, the process of frequent inspection and adaptation.

I’ve been witness to the start of hundreds of teams and projects. There’s a point at which, during the launch of a new team even before the first Sprint, I can tell with fair certainty whether the team will be successful or not.

History