How to Ship in 8 Weeks or Less (via Cross-Functional Teams)

How to Ship in 8 Weeks or Less (via Cross-Functional Teams)

Bored of Scrum and Kanban? Thinking about making the move to Shape Up?

This post is here to get you clued up on what the development methodology Shape Up looks like in practice. I’ll be giving you a sneak-peak into what we do here at Process Street as our EPD team shares their secrets. Learn how Shape Up facilitates the smooth running of a cross-functional team.

For those of you who are unfamiliar with Shape Up, or if you’re interested in the Design part of the E-P- “D = design” team,or maybe, you’d like to get your hands on 3 Shape Up workflows to plug straight into your team, check out the following posts:

In this post I speak to Process Street’s Product Lead, Michael, and our Full Stack Engineer Herbie. We talk about all things Shape Up and discuss how the methodology facilitates the success of a cross-functional team.

Let’s get started!
Continue Reading

Shape Up vs Scrum: 6 Months to 6 Weeks – How We Cut Our Dev Cycle 75%

shape up

From sprints to cycles, and from product backlogs to …well…no backlog at all. These are just a couple of examples of the differences between Shape Up and agile approaches such as Scrum.

But, what exactly is Shape Up? How does it, when put into practice, differ from Scrum?

Our development team here at Process Street recently made the move from Scrum to Shape Up and I asked them how the two compare. This post outlines the key takeaways from the team and takes a closer look at what Shape Up is as a whole.

To jump to a specific section, click the appropriate link below:

Alternatively, to read the whole post – just keep on scrolling. 🚀
Continue Reading

What is Scrumban? The Best Parts of Scrum and Kanban

scrumban
507 blog posts.

That’s how many items our team has created, edited, and published since implementing Scrumban.

Before we set up our system, we were mostly scrabbling to get items together from week-to-week, without knowing what we’d be working on next.

Now, we’re always 3 weeks ahead of our publishing calendar, have built our blog to over 130,000 subscribers, and have expanded our team by over 300%.

That’s why we here at Process Street will take you through this (practically new) method for managing your team and projects.

We’ll cover:

If you want a sneak preview of how we’ve deployed Scrumban, I’ll give you a hint. It’s got something to do with the Sprint Planning checklist below (which you can grab for free!)…

Let’s get started!
Continue Reading

Kanban vs Scrum: Understanding the Tools for Agile Success

Kanban vs Scrum

You’ll often hear the question: “Which is better? Kanban or Scrum?” or variations of this eternal deathmatch between two of the most well-established agile methodologies.

People are wasting energy fighting over which methodology trumps another. If you’re an agile organization, you should be placing principle above practice.

It makes a lot of sense to ask questions like “why might I want to use Kanban over Scrum?”, or even “Kanban and Scrum” as opposed to “Kanban vs Scrum”. There are a lot of differences between the two, but fundamentally, they are both agile methodologies, and the principle behind why you might want to use both can be in alignment.

You may even find they can work well together, as part of a unified strategy referred to as Scrumban. You need to consider what approach will work best for your team.

My aim with this article is to approach the question of “Kanban vs Scrum” by clearly presenting both approaches in terms of when, how, and why you might choose to use either of them.

I’ll also talk about the capacity for overlapping Kanban and Scrum approaches, and how some additional tools like Process Street can factor into that equation.

Here’s a breakdown of how we’ll approach comparing “Kanban vs Scrum”:

Let’s start with a basic primer on what it means to be agile. Continue Reading

What is Fake Agile? Understanding the Dark Side of Agile and How to Avoid It

fake agile

Agile is a buzzword. These days, everyone is “doing agile”. Or so they say.

Despite over 90% of senior executives stating agile adoption as a top priority, less than 10% actually consider their firm to be performing with a high level of agility.

As much as people love to wear the badge of agile on their sleeve, there is a great deal of confusion swelling in the dark chasm between the aspiration of agile implementation and reality.

So what is agile?

It’s basically a philosophy of software development that prioritizes iterative development of working software and solutions through cross-collaboration and self-organizing teams.

It’s also an umbrella term for a bunch of development frameworks, but agile doesn’t simply mean kanban or scrum.

Some of the confusion arises when teams equate the agile approach to using an “Agile framework” (usually capitalized).

Frameworks like these are attractive because they’re sold as simplified solutions to difficult project and process management problems.

Sure, these frameworks can be an important part of an agile implementation, but they need more. They need a firm foundation to stand upon.

It’s not enough to simply go through the motions and expect an agile approach to “just work”, especially when transitioning from a more rigid and traditional framework like waterfall.

In order to drive agile success, teams need to adopt agile philosophy. They need to change the way they think about work ownership, management, and their relationship and duty to customers.

Without this vital force, frameworks like scrum and kanban fall flat.

In this article I’ll investigate what it is that separates true agile from the “fake” agile that is often the differentiator between success and failure of a development team. Here’s a quick overview:

Continue Reading

Get a free Process Street account
and take control of your workflows today.

No Credit Card Required