Skip to main content

Scrum in a Creative Context


As a "creative" i.e. a designer of things and ideas, not software, is it possible to come to great results that fulfils wishes, excites and comes to market quickly even under the atmosphere of big uncertainty that is characteristic for creative projects?

As a creative, you know the answer has to be "Yes!" Are the approaches that you are using to manage and plan work, create ideas, collaborate with the customer to make the ideas even more awesome, are these practices effective? If you have watched an episode of Mad Men, you know the answer is "No!" Want to find a better way? 


Learn, explore and find a better way with leaders!

We are a small team consisting of Design Manager Sandra Islam, Roland Sailer, a partner of the branding agency NOSE, and Peter Stevens. We believe something like Agile and Scrum is going to become the standard approach for creatives.

Software development is a complex and creative process, which is often poorly understood by those asking for software products. Sound familiar? "Agile" "Scrum" and "Lean" values, principles and practices have enabled software developers to become more creative, more effective and have more fun at work. They have been the basis for everything from more efficient manufacturing processes to more effective organizational transformations.

Can they help creatives do the same? We think so! We are looking for a few pioneers to explore Scrum, Lean and Agile with us, to create new and better ways of working in a creative context.

Here's the plan

  1. June 14/15: Learn about Scrum - you'll become a Certified Scrum Master in this course in which we'll take a special look at the needs of Creatives who are not doing software.
  2. June 25: Take it to the next level - Scrum and Agile work in software, but the work of creatives is different. How do you tackle the challenges of a creative environment? This is a one day workshop, not a course, and not a PowerPoint binge! We'll identify the challenges together and come up with solutions together, so you can start improving your environment right away!

How to participate

We've made it easy for you! The course is on a weekend, so you don't have to take time off from work. Since we're creating something new, you might not sure of the value, so we have decided to make special pricing available, so pricing won't be an obstacle either! Here's what you do:
  1. Contact me to ask about special pricing (or other questions)
  2. Register for the Weekend CSM Course with Creatives Workshop!
  3. Get ready for the Red Pill!
P.S. Want to hear about some experiences first? Come to the the "Mad Men meets Agile" with Roland Sailer and stay for our Apéro and Vernissage! Read more for information and registration!



Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …