Winning Agile Projects is exclusively for Microsoft Business Applications partners and admission is by application only.

It's designed for partner whose delivery teams are already familiar with agile approaches, like Scrum.

It's ideal if your sales, pre-sales and engagement leadership are struggling with outdated proposal formats, long drawn estimation processes, and traditional statements of work for waterfall-style engagements.

Do any of these challenges sound familiar to you?
✔ Your proposals mention Microsoft Dynamics Sure Step?
✔ Your estimation process involves months-long discovery or initiation phases?
✔ You rely on detailed, written requirements specifications?
✔ Customers resist an agile approach because they don't understand the benefits?
✔ Customers want fixed-scope, fixed-date and fixed-cost projects?
✔ You've tried an agile approach once but it felt like something essential was missing?
✔ Your prospects are choosing other partners more often that they're engaging you?

I've been there too. I've tried selling and delivering projects based on outdated approaches, like Sure Step. Since 2008 I've won and delivered hundreds of millions of dollars of agile business applications projects. I know what it's like to pitch an agile process to a prospective customer, lead a discovery team in a rapid estimation engagement, and construct compelling, agile  proposals and contracts.

Can your team learn how to win more agile projects? Yes, then definitely can. I'd love to show you how.

Race 1: Qualifying agile opportunities

Whether you're already proposing an agile approach or not, we're going to make sure you're pitching to the right types of customers and for the right types of projects where an agile approach is most likely to lead to successful outcomes for your customer and for you. You'll also recognise what type of team you'll need within your practice for agile approaches to succeed.

At the end: You'll be able to confidently qualify customers and projects perfect for pitching an agile approach. 

Race 2: How to pitch the benefits of an agile approach

There are many benefits experienced by customers building agile apps. You'll learn about them and how to describe them to your customers this week.

At the end: You'll be able to identify and articulate the top three benefits for your prospective customer.

Race 3: Creating compelling proposals for agile projects

Through a case study of a Microsoft customer receiving two proposals, you'll learn what goes through customers' minds when they are reviewing your proposals.

At the end: You'll learn what makes a compelling proposal for an agile business application project.

Race 4: Estimating agile projects

Traditional approaches to project discovery take months and produce detailed but inaccurate documentation. There is a better way! We'll learn proven practices for reducing uncertainty at the start of a project.

At the end: You'll know how to build a user story map and release burndown chart that illustrate the goals, persona, scope, features, timeline, resources and costs of your customer's business applications project.

Race 5: Creating agile contracts

Let's try and avoid traditional contracts that bind us to an inflexible requirements specification. Instead, we're going to review an agile statement of work that focuses our joint team on achieving the customer's desired business outcomes.

At the end: You'll be able to make changes to your statement of work template so that they work for agile engagements.