Agile resource center

The Agile Development Methodology in Practice.

Mastering agile and the Scrum Methodology within your development organization is likely to require some trial and error as no two organizations apply the method the same way.

Introduction to Agile Development

Why? A few reasons:

There are gaps in agile and the Scrum methodology as relates to the software development lifecycle. For example, nothing in the official Scrum Methodology covers release planning or release estimation.

  • Within the Scrum Methodology there are decisions to make such as the length of sprints and when NOT to use Scrum and, instead, use a different agile methodology such as Kanban.
  • Whether to use an agile overlay to the Scrum Methodology for larger development organizations such as Scaled Agile Framework (SAFe) or Large-Scale Scrum (LeSS).

The CodeStringers Agile Software Development Resource Center will cover some of these topics, but not all. If you’re interested in having one of our executives be a sounding board or consultant to help implement agile or tune your organization’s implementation of agile, let’s talk.

Full Agile Primer Video.

This video is an hour and 10 minutes long and includes a detailed review of agile and the Scrum Methodology, along with tips that agile does not prescribe. Our tips will enable your organization to build better software faster, hit critical milestones, and execute with complete transparency into the process and development status within your company.

In this series

Read the white papers.

Questions

Questions people ask.

What is the agile development methodology?

Agile is a way of building software in short increments, each producing working software that users can react to, so that the plan changes as the team learns rather than being fixed up front. It values individuals and interactions, working software, customer collaboration and responding to change over the processes, documents, contracts and plans that traditional methods centre on. Scrum, Kanban and several scaled frameworks are specific methods for applying those values.

What is the difference between agile and Scrum?

Agile is the set of values and principles; Scrum is the most widely used method for putting them into practice. Scrum defines three roles, product owner, scrum master and the team, a set of ceremonies such as sprint planning, daily stand-up, review and retrospective, and artifacts such as the product and sprint backlogs. A team can be agile without Scrum, for example on Kanban, and a team can run Scrum ceremonies without being agile in practice.

When should you use Kanban instead of Scrum?

Kanban suits work that arrives continuously and cannot be planned into fixed sprints: support, maintenance, operations and teams whose priorities change daily. Work flows through a board with limits on how much is in progress at once, and items are pulled as capacity frees. Scrum suits building a product in planned increments with a stable team. Many organisations run Scrum for product development and Kanban for the teams that keep systems running.

What do SAFe and LeSS add to Scrum?

Scrum describes one team. The Scaled Agile Framework and Large-Scale Scrum are overlays for organisations with many teams working on one product or portfolio. They add coordination across teams, shared planning cadences, portfolio-level prioritisation and roles that Scrum does not define. SAFe is the more prescriptive of the two; LeSS keeps closer to plain Scrum with as few additions as possible. Neither is needed for a single team or a small company.

Does Scrum cover release planning?

No. The official Scrum method's largest increment is a sprint, and nothing in it covers planning or estimating a release that spans many sprints. Businesses still need release dates for marketing, sales and operations, so teams overlay release planning on Scrum: story mapping, a product backlog for the release, an initial estimate and then velocity-based re-estimation as sprints complete. That overlay is one of the gaps where organisations apply the method differently.

How we start

Most of our best clients come to us with a feeling, not a plan.

"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.