Why it’s so important to learn ATDD upfront

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”

Why you should go beyond the Scrum Guide with Scrum

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”

Scrum FLEXed

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”

Scrum should be specialized for software development/IT teams

Software is not the same as the physical world. While work in the physical world is often visible, in the software world it often isn’t. Consider how you can see what’s being built in the physical world, but in the software world, writing bugs or good code looks the same. Continue reading “Scrum should be specialized for software development/IT teams”

Pay for your Agile adoption with the waste you eliminate by focusing on Agile Product Management (APM)

The intent of APM is to identify the most valuable work to be done, focus on just that work, prepare it for the teams to work on &guide them in building the functionality needed in thin slices. This creates quick feedback, the ability to pivot & faster value realization.  The goal is business agility–the quick realization of value predictably, sustainable &w/high quality. Product management creates clarity on what is most valuable for the organization to build while providing teams guidance in its implementation. By discovering & removing unnecessary scope and providing this slices of work, teams become focused on true value delivery while becoming more efficient. This enables dramatically shorter times from start to initial value delivery.

Continue reading “Pay for your Agile adoption with the waste you eliminate by focusing on Agile Product Management (APM)”

Adopting Agile in an Agile Way

The Agile Manifesto suggests our highest priority is to maximize value delivered. This requires looking at the potential increments of value delivery and determining what items provide the greatest value for their cost. Agile development often uses “time-boxes” (Scrum’s sprint) to provide a framework for delivering complete chunks of value in a short time. Continue reading “Adopting Agile in an Agile Way”

How Lean can make SAFe and/or Scrum adoption faster, better, cheaper

I have decried calling Lean “faster, better, cheaper” because “faster” is not the goal as much as removing delays with the result being “quicker”. I also think the focus is on quality &being effective. But in SAFe &/or Scrum adoption, Lean provides a different perspective than the standard focus on certification &frameworks, &maybe “faster, better, cheaper” is the right moniker. Continue reading “How Lean can make SAFe and/or Scrum adoption faster, better, cheaper”

The Agile Coaching Manifesto: The Agile Manifesto re-written for Agile consultants

We have come to value:

  • Individuals and interactions over PowerPoint presentations
  • Actual increased ability over understanding frameworks
  • Helping students over following a set curriculum
  • Adjusting to needs of the student over preparing for certification
  • Our highest priority is to increase the ability of the student through early and continuous learning
  • Welcome changing needs of students, even late in the course. Agile courses harness change for the learners’ advantage
  • Deliver small, absorb-able increments so the students actually learn
  • Teach individuals on their own projects and in their own environment. If they stagnate, trust that they are doing their best and see how to help them.
  • The ability to create software of value is the primary measure of progress.
  • Agile teachings promote sustainable learning.
  • Continuous attention to Agile skills enhances agility
  • Simplicity–the art of maximizing the amount not required to teach–is essential.
  • The best learning paths are those that allow for ability to emerge by attending to skills that enhance future learnings.
  • At regular intervals, the consultant reflects on how his students are doing and adjusts the curriculum as needed.