Start Your Project With a Walking Skeleton

14. April 2018
Kategorien
Newsletter abonnieren

Start your project with a Walking Skeleton

In order to reduce risk on large software development projects, you need to figure out all the big unknowns as early as possible. The best way to do this is to have a real end-to-end test with no stubs against a system that’s deployed in production.

You could do this by building a so-called Walking Skeleton, a term coined by Alistair Cockburn. He defined it as a tiny implementation of the system that performs a small end-to-end function. It need not use the final architecture, but it should link together the main architectural components. The architecture and the functionality can then evolve in parallel. A similar concept called “Tracer Bullets” was introduced in The Pragmatic Programmer.

A Walking Skeleton is a tiny implementation of the system that performs a small end-to-end function. It need not use the final architecture, but it should link together the main architectural components. The architecture and the functionality can then evolve in parallel.

If the system needs to talk to one or more datastores then the walking skeleton should perform a simple query against each of them, as well as simple requests against any external or internal service. If it needs to output something to the screen, insert an item to a queue or create a file, you need to exercise these in the simplest possible way. As part of building it, you should write your deployment and build scripts, set up the project, including its tests, and make sure all the automations are in place — such as Continuous Integration, monitoring, and exception handling. The focus is the infrastructure, not the features. Only after you have your walking skeleton should you write your first automated acceptance tests.

This is only the skeleton of the application, but the parts are connected and the skeleton does walk in the sense that it exercises all the system’s parts as you currently understand them. Because of this partial understanding, you must make the walking skeleton minimal. But it’s not a prototype and not a proof of concept — it’s production code, so you should definitely write tests as you work on it.

High Risk First 

According to Hofstadter’s Law, “It always takes longer than you expect, even when you take into account Hofstadter’s Law”. This law is valid all too often. It makes sense than to work on the riskiest parts of the project first, which are usually the parts that have dependencies: on third-party services, on in-house services, on other groups in the organization you belong to. It makes sense to get the ball rolling with these groups simply because you don’t know how long it will take and what problems should arise.

Making changes to architecture is harder and more expensive the longer it has been around and the bigger it gets. We want to find mistakes early. This approach gives us a short feedback cycle, from which we can more quickly adapt and work iteratively as necessary to meet the business‘ prioritized list of runtime-discernable quality attributes. Assumptions about the architecture are validated earlier. The architecture is more easily evolved because problems are found at an earlier stage when less has been invested in its implementation.

The bigger the system, the more important it is to use this strategy. In a small application, one developer can implement a feature from top to bottom relatively quickly, but this becomes impractical with larger systems. It is quite common to have multiple developers on a single team or even on multiple, possibly distributed teams involved in implementing end-to-end. Consequently, more coordination is necessary.

No Shortcuts

It’s important to stress that until the walking skeleton is deployed to production (possibly behind a feature flag or just hidden from the outside world) you are not ready to write the first acceptance test. You want to exercise your deployment and build scripts and discover as many potential problems as you can as early as possible. The Walking Skeleton is a way to validate the architecture and get early feedback so that it can be improved. You will be missing this feedback if you cut corners or take shortcuts.

In a nutshell: Start with a Walking Skeleton, keep it running, and grow it incrementally.

Tags

Das könnte Sie auch interessieren

Going Live Too Early Can Be Worse as Going Late

15. Februar 2021

Large transformation programs rarely collapse without warning. They collapse because the warning signs are ignored. In post-mortems, the pattern is almost always the same. The project team knows the system is not ready. The risks are visible. The defects are known. The dependencies are fragile. Nothing is hidden. And yet, the decision is made to

Weiterlesen

Another Great Leading Indicator for Future Trouble – Issue Resolution Time

10. Februar 2021

I have a very simple metric for determining the health of a project or an organization: the age of issues.  Issues are like fish; when they get old, they stink.  A sure sign of a lack of leadership and upcoming trouble is old issues or issues that take longer than necessary to resolve.  Issues are

Weiterlesen

A Great Leading Indicator for Future Trouble – Missing Milestones

31. Januar 2021

I have done quite a number of inflight reviews and post-mortems of troubled and failed large system implementation projects.  One pattern that emerges very clearly is the one of missing milestones whilst keeping the go-live date the same.  It rarely ends well. I see it again and again. Multiple important milestones are missed. Sometimes by

Weiterlesen

Can a Task Force Rescue Your Failing Project?

9. Januar 2021

We’ve all witnessed projects in trouble—the ones that required a quick and firm intervention in need of help from a task force to bring it back on track.   No executive wants to be in such a difficult situation, especially not with one of his or her own projects.   But how do we, as

Weiterlesen

How a Transformation Office Can Help Your Transformation Initiatives Succeed

2. Januar 2021

A new year has just started, but also in 2021 companies will be talking about digital transformation often. I think digital transformation is a terrible description for what is just another transformation. See my article “Digital Strategy Does Not Exist” on why that is.    But we shall use the term for a moment to

Weiterlesen

Project ≠ Program ≠ Portfolio ≠ Strategy

13. Dezember 2020

I have had many heated discussions around these terms. People mix these up and it confuses your organization and its people.  This is my take on it.  If your organization is running many projects at the same time it is impossible to make the right decisions if all projects are performed in isolation. Therefore projects

Weiterlesen

Project Failure Is Largely Misunderstood

26. November 2020

For many years, organizations, researchers, and practitioners have analyzed how to manage technology projects successfully.  Among them is the Standish Group, which regularly publishes its findings in its Chaos reports. In 1994, Standish reported a shocking project success rate of only 16 percent; another 53 percent of the projects were challenged, and 31 percent failed

Weiterlesen

User Enablement is Critical for Project Success

14. November 2020

Systems do not create value. Usage does. You can implement the most advanced CRM, ERP, or core system on the market. If your organization does not use it properly, the return will be marginal at best and negative at worst. Data quality drops, processes fragment, workarounds emerge, and the old ways of working quietly reappear

Weiterlesen

When IT Owns Business Decisions, Value Disappears

18. Oktober 2020

Executives do not struggle with IT because they do not understand technology. They struggle because they have delegated decisions they should never have delegated in the first place. The frustration is familiar. Technology costs keep rising. Capabilities expand. Programs consume time and attention. And yet, the business impact remains unclear or disappointing. Systems go live,

Weiterlesen

What Executives Need to Know About Project Management

11. Oktober 2020

I work exclusively with executives and when there is one thing that I have learned over the years is that effective executives have at least a basic understanding about project management and their roles in it.    When you look in a dictionary for the word «executive» you will find an entry similar to the

Weiterlesen