When we formed Wildebeest in 2014, our goal was to build transformative products for clients that would empower their customers. Software was our medium, and the possibilities were (and still are) endless.

But a lot has happened since then. With recent wins at Cannes Lions, The One Show, Webby Awards, ADC, and D&AD, our team already excels at balancing innovation with polish. We’ve been at the helm of some truly inspired projects.

• With emerging technologies, we’ve had the chance to develop one-of-a-kind experiences utilizing AR (Cheetle ID), Machine Learning (NCAA & Google), and Computer Vision (Cox Automotive)
• For projects where the primary goal is business transformation, we’ve worked with notable brands on mobile applications (PBS), dev team augmentation (GoodRx), and even full design and development projects (Solidigm)

What we discovered was that being a great software development agency wasn’t enough. In order to really create something that puts the power back into people’s lives, we needed a process that matched up with our ability to make great software. We knew there were drawbacks with traditional dev agency engagements that ultimately hindered our ability to make great products.

So we developed Ready, Set, Go, a repeatable project engagement framework that ensures efficiency and thoughtfulness along every step of the development lifecycle.

Before Ready, Set, Go

If you approached us years ago, we probably walked you through the traditional scrum process. We likely would have talked about the 5 D’s: Discovery, Design, Development, Delivery, and Debrief.

We probably pushed for a fixed deliverable/fixed budget project structure to minimize waste, prevent scope creep, and keep our projects on track.

Within the traditional dev project model, that’s one of the only guardrails against scope creep and resource depletion. Unfortunately, a fixed structure is also the best way to stifle creativity, flexibility, and agility in the development process.

If we really wanted to make remarkable products, the fixed project model needed to go; it made it difficult for us to handle changing project needs and created a lot of administrative hurdles that ultimately cost us more time on the project and our clients more money.

The Need for a New Project Framework

As we continued to lean on the traditional project framework, not only did we keep hitting the same roadblocks, but we also found that it was having a negative impact on team morale.

People (clients and our developers/creatives) felt like they had limitations and couldn’t collaborate freely. This tends to drive developers and creatives crazy. As a software development agency, one of the biggest business challenges is managing great talent, so we needed to give them more freedom to flex their skills.

On the client side, the traditional project engagement model required more work and more protocol to follow for changes or iterations, which often negatively impacted project sentiment and outcome.

At the end of the day, both parties were forced to utilize a project methodology that wasted creative expertise, budgets and burned through valuable (and costly) team hours.

Ready, Set, Go

The beauty of the Ready, Set, Go framework is that it allows us to assemble dedicated teams to embed with your project team, who will eat, breathe, and sleep your unique business challenges.

How It Works

1. Before any code is written or design time is spent, we ensure that consultants and clients are entirely aligned on the research and the strategy it informs–we call this Ready.
2. Once the strategy is in place, Set is a focus on planning that lays out the roadmap, epics, and sprints that will soon guide the way. At this point, consultants and clients will be precisely aligned on the vision and approach so Go can begin.
3. Go is a traditional scrum development process that we will lead to cycle through the product roadmap in two-week agile sprints. As changes are made, or new information is discovered, this lightweight process gives our team the flexibility to course-correct without the need for costly change requests.

When a Go cycle ends, we can seamlessly hand off the project to the client team, or we can repeat Go as many times as we need — something that the previous fixed project model didn’t allow for.

With Ready, Set, Go, we can iterate as fast and often as the client wants, resulting in better project outcomes, less budget waste, higher team sentiment, and a more successful partnership.

Fixed budgets and fixed deliverables simply cannot.

CONTACT US TO LEARN MORE

As we introduce existing and prospective partners to Ready, Set, Go, we understandably get a lot of questions. Below are a few ways to think about the Ready, Set, Go project framework and how impactful it can be for your business.

Current Dev Partner Red Flags

Don’t saddle yourself with an inefficient process and an ineffective development partner when you have specific, audacious goals to meet.

If you’ve encountered any of the scenarios below, then it might be time to give us a call:

“Let’s start the coding process as we finalize the requirements for the full project. We can always back into the end product….”

Writing code before you have discussed and agreed upon all requirements is a great way to waste weeks of valuable dev team time and costs.

“We’re still working through tickets to finalize revisions on the MVP, but we can’t share the updated version with your team yet. Let’s plan on sharing it next week….”

A lack of visibility into the development process means that you — as the client — won’t be able to request changes or iterations until work has been completed on an existing prototype. That means more time was wasted on an end product that’s going to require more time and money to get right. You’re also more likely to miss key milestones along the development lifecycle.

“If you have a question or issue, just email John, and he’ll get it to whoever is in charge. He owns that part of the project….”

A clear and defined ticket system is how the most efficient and on-deadline projects are run. If you’re working with a dev partner who foregoes a clear ticketing system, you’re going to waste time and money.

“We don’t have visibility into how this project is pacing internally, however, we can give you notes from our weekly stand-ups if that helps….”

There’s no way to gauge a project’s success without adequate reporting. This is another area where inept dev projects love to hide. Don’t let it happen.

“I oversee the dev and UX teams. I’m also going to be the project manager for this sprint….”

There’s a time and place for a “product generalist,” but it’s not in the middle of a professional dev project. Your dev partner should have the best people doing the work that they’re destined to do.

“We weren’t aware that you guys wanted an app-specific implementation, and it’s technically out of scope. We’ll need a project addendum and additional budget….”

Poor planning and inadequate estimates will always require change orders, paperwork, and more money. Execution is all about ensuring that you’ve got a clear understanding of the project plan, needs, and outputs.

What Ready, Set, Go Looks Like from the Outside

If you’re a stakeholder and only seeing the outward-facing results of a Ready, Set, Go engagement, here’s what it will look (and feel) like from the outside:

• More consistency in product releases and product quality
• Higher sense of visibility into project progress and end-product roadmap
• Bi-weekly product iterations
• Better team morale during the project for client teams and Wildebeest as your dev partner
• A greater sense of freedom and flexibility in project planning
• Less friction for unplanned iterations
• Fewer change orders and disruptions to project scope

What Ready Set Go Looks like from the Inside

If you’re part of the team that works with us as a development partner, here’s what Ready, Set, Go projects look (and feel) like from the inside:

• Crystal clear internal expectations are set via sprints in the project roadmap
• Higher internal team morale
• Better division of labor between partners, devs, project leaders, and stakeholders
• Less of a need to “rush” to complete sprints during the process
• Fewer restrictions and red tape around time and project budget
• More flexibility during QA and iteration
• Better transparency up and down the project ladder
• A more productive and exciting project overall

CONTACT US TO LEARN MORE