I founded Net Objectives almost 20 yrs ago. I have always loved solving problems and having a chance to earn a living by helping others solve problems has been a very wonderful opportunity for me. Continue reading “A personal goal of almost two decades is manifested today”
Many people think of Acceptance Test-Driven Development (ATDD) as an advanced practice. Others think that using Given When Then (GWT) from Behavior Driven Development (BDD) requires the use of tools. Neither of these are true however. The easiest way to start using ATDD and/or BDD is simply to ask the question “How will I know I’ve done that?” whenever you are given a requirement – even if the requirement appears to be obvious. The reason for this is that it is often the ‘obvious’ requirements that are most misunderstood. Continue reading “When given a requirement ask the question, “How will I know I’ve done that?””
I founded Net Objectives almost 20 yrs ago. I have always loved solving problems and having a chance to earn a living by helping others solve problems has been a very wonderful opportunity for me.
I have long thought that training methods have had to change significantly to keep up with the growing demand. It has in some ways – simulations, games, group exercises, etc. But basically, training is how it has always been. Especially in the area of growing Scrum Masters or Agile Team Coaches. In particular provide 2-4 days of coaching and then either let them go on their own or pay a lot of money for a coach. Continue reading “A personal goal of almost two decades manifested today”
One of the central tenets of Lean is that the system people are in impacts them significantly. This does not mean, however, that one can just create a new system and put people in it – this would be a perversion of Lean-Thinking. Lean suggests systems support our people. But this presumes they are capable of getting their work done. Putting people into a potentially Agile system does not teach someone actual Agile skills.
If you are kicking off new teams there are two types of coaches you can bring in. While it’s useful to bring in someone who can actually help with the work, such as a technical or ATDD coach, when it comes to Scrum or Agile coaches it’s usually better to grow your own. There are several reasons for this:
Which initial training you chose should therefore be that teams can do this after their initial training. The promoted belief that you should focus on the framework & then learn how to do this later is not just self-serving, it is wrong. While you can take a course and then pay for coaching after the workshop to learn this is not just expensive but wastes the time of your staff and often produces resistance. Continue reading “The #1 challenge for teams after Scrum training is writing small, well-scoped, testable stories”
First, let’s be clear what we mean by Acceptance Test-Driven Development. It does not mean automating testing. It means to collaboratively (Product Owners, devs and testers) working together to go from features to small stories (less than three days) that are well-scoped and have clear acceptance criteria that could be automated if desired.
Most companies delay ATDD because CSM and team level courses for SAFe don’t include it. The trade off is more framework and less actual Agile work. Continue reading “Why it’s so important to learn ATDD upfront”
The Scrum Guide is the de facto standard for how to do Scrum for Scrum.inc.org.alliance. But at Net Objectives we believe you can and should go beyond it – pragmatism over dogmatism – work over framework.
There is, of course, a reason that the Scrum guide says “Scrum’s roles, events, artifacts, and rules are immutable.” And, if you are starting Scrum out on your own and you have control over your team that’s likely a good thing. But when Scrum doesn’t exactly fit, relaxing the rigor in the right way can make Scrum more effective. Continue reading “Why you should go beyond the Scrum Guide with Scrum”
Do you have devs who resist Scrum or don’t want to take the time to write better code? I can attest that with very few exceptions devs want to do the right thing in the right way. So why does it show up differently?
Several answers: Continue reading “Attend to what’s in it for them”
Scrum’s roles, events, artifacts and rules are immutable. Ironically, immutability is as non-Agile as one can be – so why is this? When difficulties arise in how work is being done a question must be asked – “are we doing the right thing poorly or just doing the wrong thing? Scrum pre-defines the “right” thing & says keep working on until you do it correctly. But what if these are not ideal for your situation? What do you do then? Continue reading “Scrum FLEXed”