How to Use

An instruction chart on chess pieces and how they moveContents

Approaching Agility

Full Scale agile™ is a complete system for agility-at-scale, which means it can serve any need that brought you to this site. Whether you want to harness the power of agility for one team, transform your entire company/agency, or anything in between, FuSca™ gives you the background information and step-by-step instructions to do it.

This website provides a package of five overlapping approaches to agility, some of which can be combined with others:

Approach Description Notes
Self-Directed agile The preferred method walks groups through the process of becoming fully self-directed teams that create their own agile processes to meet customer needs.
  • Team can choose to follow any other package as well.
  • Scrum and Kanban teams benefit from writing a Team Charter per this approach, even if not becoming self-directed.
FuSca Light A light, easily implemented version of Scrum intended for startups but helpful for any team wanting better work management without the discipline (and benefits) of a more detailed method.
  • Self-directed teams can save time by adopting and adapting this rather than creating work management processes from scratch.
  • A good “bridge technique” to later adoption of full Scrum or Kanban, if desired, or to fully customized processes.
Sprints The FuSca version of full Scrum, with psychology-based enhancements to fix common problems seen by Scrum teams. Though useful for single teams, intended for larger organizations wanting to coordinate the work of multiple teams quickly.
Kanban The FuSca version of a method intended for teams doing highly repeatable work that can be completed by a single person in less than a day. Not designed for project work requiring high degrees of coordination between people with different skills sets.
Release Planning A Scrum-based method for mid-term work planning of outputs requiring closer coordination of multiple teams across longer time periods than a sprint, such as hardware/software products or construction. Based on throughput of requirements, and thus can be applied to teams using any of the previous three approaches or non-FuSca versions of Kanban and Scrum.

The site complements these with information on agile transformation, enterprise-level changes, and more, as detailed below.


Review these scenarios to see which one applies to you, and follow the relevant link:

  • New to Agile or only know a little about it—Learn the basics with Agile 101.
  • A new or pre-existing team that wants to create its own approach to agility—Go to “Self-Directed agile.”
  • A startup of 4 to 12 people needing a shortcut to getting organized with the help of a light process—Go to “Agile for Entrepreneurs.”
  • A change agent evaluating our evidence-based approach to formal Agile—Read the entire “System” section like a book, following the link at the bottom of each page to the next one.
  • A team or group of teams that has already decided (or is being required) to adopt FuSca—Go to “The Sprint Process” (Scrum, for project teams) or Use Kanban for Flowing Work.
  • A team or group currently using Scrum but adding release planning—Go to “Plan in Releases.”
    Note: Teams must have a stable velocity (whether story points or counts), and be able to meet the Agile Performance Standards with existing practices. If not true for you, see the previous bullet for changes to consider.
  • New major initiatives (programs or projects)—Go to “Initiate Agile Programs,” whether using new or existing teams.
  • A larger organization that wants to adopt a system of Agile (not necessarily FuSca or the entire enterprise)—Go to “A Process for Agile Transformation.”
  • A larger organization adopting FuSca—While using the process above:
    • Consider the changes described in “Create an Agile Enterprise” during Epic 3, “Determine Organizational Readiness,” especially the recommendations under “Structuring for Agility.”
    • Skip Epic 8, “Choose an Agile System,” and simply follow the relevant FuSca steps to implement epics 9 through 11 at the team and program levels.
      Note: You will still need to add user stories in the change project list for changes at the organization/enterprise level.

About FuSca | → Why FuSca?

Share this page