Next course Melbourne on 9-10 December 2019
About the course
Because there is no point in having a “hyper productive team” that’s building the wrong thing.
Now that Agile is fast becoming the default way of working, the world is going to need more Product Owners.
If you’re ready to start building the right things, then the LASTing Benefits Certified Scrum Product Owner (CSPO) is the course for you. It’s not just about becoming a Product Owner, it’s about becoming A Great Product Owner.
A Product Owner that not only provides the Team with direction, but also takes an active role in keeping them on course.
Making sure that whatever the produce, matters.
After all, it really doesn’t matter how fast you’re rowing if you’re going in the wrong direction.
Executing the Product Owner role well is foundational to succeeding with Scrum. It’s the Product Owner who exerts the strongest influence on both what is built and when it is delivered; ensuring that both customer and stakeholder needs are met.
Scrum is a simple, but powerful framework that specifies only three roles. However, hidden behind this simplicity is science, experience and sophistication. With only three roles to choose from, getting the best out of Scrum means implementing each of these roles as well as they possibly can be within constraints laid down by the objectives of your personal and organisational context.
Many of most powerful and transformative benefits of Scrum lie in the way that traditional areas of focus and responsibility have been carved up anew; balanced and redistributed between the three Scrum roles. Missing this subtle but important point is an increasingly common mistake, which leaves people confused and frustrated as they struggle to fulfil the duties of a poorly considered interpretation.
Perhaps more than any other role, the Product Owner has the potential to create the kinds of benefits that your customers and stakeholders will really notice. Whilst velocity is nice, it’s not as meaningful as results.
Product Ownership is not a role to take lightly, implement poorly or leave up to chance. That’s why in 2008, the Scrum Alliance launched the Certified Scrum Product Owner (CSPO) certification to live alongside the venerable and industry leading Certified ScrumMaster (CSM). Shining a spotlight on this vital but often neglected and misunderstood role; helping people succeed as Scrum moved into new industries, new contexts and new levels of scale.
LASTing Benefits (Australia, UK) has been on this journey with the Scrum Alliance from the very beginning, and as such, is one of the most experienced providers of Scrum Product Owner training and coaching services in the world.
Who should attend?
The course is open to all. There are no prerequisites or pre-reading required. All you need is an open mind, a desire to succeed, and maybe a pen.
In our experience the following kinds of people get the most benefit from attending1:
- Prospective Product Owners wanting to prepare for their upcoming role
- Practicing Product Owners wanting to hone their craft
- Traditional Product Managers wanting to know what all this Product Ownership business is about
- ScrumMasters wanting to broaden their knowledge of Scrum
- Managers of all kinds wanting to improve how they select, work with and manage Product Owners
- Stakeholders of all kinds wanting to better understand Scrum from a business perspective and how to get their needs met
- Customers wanting to better understand how Scrum works and what is expected of them
- UX, UI, & BA – a trio of roles long neglected by Agile. Whether you’re wanting to learn how to work with, or become a Product Owner, this course will give you the practical and definitive answers you’ve been looking for.
- Traditional Project Managers wanting to better integrate with existing Scrum Teams or wanting to pivot into Product Ownership.
- Anybody curious about Design Thinking in general or more specifically how it works with Scrum.
Over the years, some of our greatest agile success stories started with Product Owner / Client pairs attending one of our CSPO classes together. It’s a great environment in which to better understand the process, talk through real world issues as well as explore and define what is expected of each party.
We’re constantly being told how much more trust and enthusiasm clients have in the Scrum way of working after attending one of our classes. More than one client has arrived a sceptic and left an evangelist.
So feel free to “double date”!
You will learn…
A Product Owners Perspective on Scrum
Learn how to see Scrum not as a series of baffling rituals and obscure artefacts, but rather from the Product Owners perspective; as a tool that helps you stick to schedules, manage risks and generate business value quickly and effectively.
Learn which parts of Scrum are essential to the Product Owner, and which can safely be left to the Team and ScrumMaster to manage on their own.
Make better use of your time
The Scrum practices are based on the assumption that the Product Owner’s time is both limited and valuable, so these practices were explicitly designed to make the best possible use of this valuable resource.
Many implementations have however sadly forgotten this fundamental design principle to the detriment of everybody.
If you’re a Product Owner that feels that “Scrum has too many meetings” — then this is the course for you.
The Purpose of the Product Owner
Product Ownership was born in Scrum and was created for a specific purpose, in order to solve a particular problem common. The responsibilities and authority subsequently granted to the role grew from this purpose.
Developing an understanding of this purpose is key not only to performing the job well, but also to:
- Working productively with other members of your Team
- Working effectively with your ScrumMaster
- Keeping stakeholders, users and customers happy
- Implementing Product Ownership well in any context
- Scaling the Product Owner Role efficiently and effectively
Lean how the Product Owner role differs from…
- A Business Analyst
- A Project Manager
- A Product Manager
- A User Experience Designer (UX)
- A User Interface Designer (UI)
- A Customer
- A User
- The XP Onsite Customer
- A Subject Matter Expert
Whilst any of these people could be and often is a Product Owner, the term Product Owner isn’t a synonym for any of them.
Learn why, and how a Product Owner works with each of these kinds of roles (and more!) And what it means for you if you already perform one of these roles and have recently been told that you’re also now the Product Owner.
How to choose a Product Owner
The guidance on who should fill the Product Owner role has been clear from the very beginning. There are no mysteries here.
Learn how to choose the ideal Product Owner as well as how to optimise around the reality of the “perfect” choice not having been made. Especially when that choice is you!
How the Product Owner, ScrumMaster and team work together to produce amazing results
The Product Owner and ScrumMaster are the double act of Leadership and Management in Scrum. Each role has well defined areas of focus, authority and responsibility. Getting this relationship right is key to both successful project outcomes and for building industry leading organisational capability. Having a good working relationship with both your ScrumMaster and your Team is essential to getting the best out of Scrum and producing great results.
You will learn:
- What to expect from your ScrumMaster
- What to expect from your Team
- What to pay close attention to and what to delegate
- The Boundaries of Authority between each role
- Key Collaboration Points
- What to do if you don’t have a ScrumMaster
Many of our attendees tell us that the most surprising and valuable benefit they got from our CSPO training was just how much they learned about the ScrumMaster role!
How Organisational and Industry Context Affects Product Ownership
In the last 40 years, Scrum has spread far beyond its origins in New Product Development; and whilst Scrum is still ideal for this purpose in many cases Scrum Teams and the organisations they work for are doing anything but! Teams are maintaining existing products, doing BAU, “Project Work” or a mixture of all the above.
Some Teams are free to explore and experiment with seemingly limitless budgets; whilst others are constrained by rigorous “traditional governance”, perhaps as part of a “hybrid” implementation. Most people find themselves somewhere in the middle. In some cases these processes, procedures and regulations are self imposed and voluntary, being simply the product of habit and “tradition” or even just for want of a better “more agile” alternative. But for some organisations these procedures are not optional, perhaps because they dictated by law and as such are immutable.
It’s also increasingly common for customers, partners and even suppliers to be part of entirely separate organisations, sitting on the other side of contractural or geographical boundaries.
Most Scrum books and indeed courses don’t take any of these factors into account. Preferring instead to bombard students with nebulous “Best Practices” based around unfounded assumptions of what possible, or indeed necessary for your organisation to succeed with Scrum.
All these different variables combine to form the different contexts in which your Scrum implementation and Product Ownership practice needs to work effectively in. Scrum is about being the best that you can be, it’s not about randomly adopting potentially nonsensical practices from completely unrelated industries.
You will learn:
- How your context shapes your implementation of the Scrum Framework
- Tools to help you best implement Product Ownership in your context whilst still retaining as many core benefits as possible
- How your implementation affects the kinds of benefits you should expect to get from Scrum. What you should expect will get better, and what might stay the same.
The Fundamentals of Design Thinking
Design thinking is more than just beards and buzzwords, it’s a proven way of approaching product development and problem solving that produces great results and fits together beautifully with Scrum.
- What Design Thinking actually is
- The Benefits of taking a Design Thinking Approach
- How Design Thinking differs from typical enterprise approaches
- Important ways in which Traditional Design and Design Thinking differ
- How Design Thinking implementations can go wrong (pitfalls to avoid!)
- How to use Scrum and Design Thinking together
- The Role of the Product Owner in Design Thinking
Understanding the Difference between Agile Delivery and Full Business Agility
Broadly speaking, in today’s world there are two popular depths of adoption organisations are interested in when they “Go Agile” and adopt Scrum.
Many larger and more conservative enterprises are interested only in dipping their toes into the agile waters preferring to adopt what has come to be known as “Agile Delivery”
Other’s wish instead to move into “full on discovery mode” — or as it’s increasingly being called Full Business Agility.
Which approach is seen as the most desirable has some important knock on effects for Product Ownership. Whilst often sneered at by agile purists, Agile Delivery still retains some important benefits which are easily left on the table if the approach is not understood and whole heartedly embraced.
Learn the core differences between these two approaches, what they mean for the Product Owner, how you might blend them or even migrate from one to the other.
The Posture of Product Ownership
Product Ownership is more than a just a practice, it’s a way of approaching productivity that requires a special mindset in order for it to work well.
At LASTing Benefits, we call this The Posture of Product Ownership.
You will learn:
- The Mindset of the Product Owner
- How to approach your customers and stakeholders
- Dealing with “failure”
- Living and Breathing the Art of the Possible
- The Power and Pitfalls of Scrum Transparency
- How to think effectively about Velocity
- The unseen implications of the definition of done
- How to keep your focus on “The Big Picture”
- When, why and who to trust and when to insist on evidence instead
- Getting the absolute best from your team
It’s been our experience that adopting the right mindset is the key to unlocking the full potential of the Product Owner role.
Product Ownership Practices
Goal Setting and Vision Crafting
The Product Owner is above all else, a leadership role.
One of the key ways that leaders inspire others is through vividly “painting a picture” of a compelling future. As such Vision Crafting and Goal Setting are a core competencies of the Scrum Product Owner Role.
You will learn:
- The necessity and purpose of articulating a good vision
- Types and levels of Visions
- Multiple Visioning techniques
- How to create a vision even when you think there isn’t one
- The qualities of a good vision
- How to break a vision down into achievable measurable goals
- Using goals & visions to “glue” Scrum and Design Thinking together
- Goal Directed Risk Management
- How to constrain and direct your vision with role modelling
No Agile course would be complete without at least touching on User Stories. Whilst not a compulsory practice in Scrum, they are still one of the most popular and useful tools out there.
You will learn:
- The Origin and Purpose of User Stories
- The essential characteristics of a Good User Story
- How to “fix” User Stories that aren’t so good
- Useful templates for documenting User Stories
- Role Modelling for User Stories (and how Roles and Personas differ)
- When not to use Stories
- Estimating User Stories
- The how, when, and why of User Story Splitting
- Effective Acceptance Criteria
- Demystifying User Story Jargon — Themes, Epics, Sagas and more!
Creating and maintaining a Product Backlog
The Product Backlog lies at the heart of Scrum, and unsurprisingly the Product Owner “owns” the Product Backlog.
As simple as it might first appear, the Product Backlog is far more than just a simple “list of requirements” – it’s a surprisingly sophisticated tool with interesting properties used for multiple purposes. It’s not for setting and forgetting it’s a living breathing thing.
Learning how to create and perhaps more importantly maintain and manage a Good Product Backlog is the key to success with Scrum in any context.
You will learn:
- How to create a Product Backlog out of User Stories
- Efficient and Effective Product Backlog Prioritisation
- The Characteristics of an Excellent Product Backlog
- The Difference between the Product Backlog and the Sprint Backlog
- The hows, whens and whys of Product Backlog Estimation
- The Difference between Product Backlog Items and User Stories
- How to keep your Product Backlog “Well Groomed”
- The importance of an up-to-date and legible Product Backlog
- Kinds of Product Backlog Items
- Product Backlog Pitfalls. How to avoid them, how to recover from them.
The afternoon of Day Two is given over to our LASTing Benefits’ World Famous 2 and exclusive Release Planning Exercise.
“Release Planning” is the glue that bridges the gap between Agile and the Enterprise. It’s the process that provides the answer to the question some believe is unanswerable with Scrum:
“What am I going to get and when am I going to get it?”
Working as a team, students will be given the opportunity to apply everything they’ve learned so far and maybe even gain a few new insights to boot!
Our Release Planning Exercise is hands on and concrete. It makes the abstract real and joins up the dots.
We’ll start with a vision and end with not just a backlog, but a plan that we’ll have confidence in executing on.
Students have come away from this exercise calling it “engaging and transformative”. It’s so effective in fact that some organisations have licensed it from us for ongoing in-house use.
Steering with Sprint Review
Once development has started, Sprint Review is without question the most important meeting for the Product Owner to both attend and actively participate in.
It’s been our experience that even minor tweaks to your Sprint Review can provide huge benefits to your Scrum implementation.
You will learn:
- The Structure, Purpose and timing of Sprint Review
- Why it’s called Sprint Review
- How a Sprint Review Differs from a “Demo” or a “Showcase”
- When to “Showcase” and when to “Review”
- How a Sprint Review differs from a Sprint Retrospective
- The Relationship between “Done” and Sprint Review
- Who should come to Sprint Review and why
- The required outputs of Sprint Review
- The Relationship between Sprint Planning and Sprint Review
- The importance of Sprint Review to the Product Owner (and the Product Owner to the review!)
Tracking and Managing Progress
There is no greater lie in all of Agile than “I don’t know what you’re going to get, or when you’re going to get it”.
But as our managing Principal is fond of saying “I haven’t missed a deadline in 15 years”.
Learn how to plan projects, track progress and manage the three fundamental risks inherent to every software project (or indeed any project).
Just because you’re “going agile” doesn’t mean that deadlines cease to matter.
If they matter to you, your customers or stakeholders, then come learn how to manage a release in Scrum to completion.
Using the Release Plan built in the previous exercise, students will simulate managing the delivery, dealing with unexpected events, taking metrics and reporting on progress.
Additional Course Benefits
All our certified courses are fully catered, offering catered morning and afternoon breaks as well as a hearty lunch both days.
In addition we also offer the following benefits for all students.
Full Colour Printed Workbook
Containing all the courseware slides as well as additional reference material to help you continue on your journey.
Post Course FAQ (new)
Whilst we always do our best to answer any Questions students might have during the course, our trainers also need to ensure that they’ve met the learning objectives required for for certification!
So sometimes it’s just not possible to answer every question that arises during the class.
In order to alleviate this problem and create what we think is a useful resource for the Product Owner community at large, in 2019 we decided to start a FAQ section on our website.
At the end of each and every class we collect and collate any unanswered questions from the class backlog (at least the ones we can read!) and then do our best to answer them, adding them to the ever growing FAQ section of our website. Sometimes this means creating new entries and sometimes it means updating the old. Really frequently asked questions become incorporated into the course itself. Of course being a FAQ, the answers are both generalised and anonymised!
If you’ve put your contact details on your question we will however email you to let you know we’ve posted an answer to your question.
You’ll get a link to our FAQ on successful completion of your CSPO.
Two Weeks of Post CSPO “support” via email (new)
Sometimes, the most important questions don’t occur to you until after you’ve left the classroom. This is why we offer all students two weeks of free post class “support” via email.
Discounts for future training
In the 11 years that we’ve been in business, by far the majority of our business has come from people and organisations alike coming back again and again. We’d like to reward this loyalty and encourage you to become one of them by offering discounts to any student who choose to book training with us within 12 months of their last purchase.
Discounted pricing is available for both individuals wanting additional ongoing professional education or other certifications such as the CSM and Advanced CSPO as well as organisational discounts for your colleagues.
About the Instructor
Our Founder and Managing Principal, Simon Bennett, may well be the ideal instructor for your next Certified Scrum Product Owner (CSPO) course.
Here are just some of the reasons.
Over a decade’s experience in teaching the CSPO
Simon has been teaching the CSPO since its inception. Not every CST is certified to teach the CSPO and not every CST chooses to teach it either. Many CST’s are naturally Team or software development focussed, leading them to concentrate primarily on excellence in ScrumMastery or Team dynamics. While this is both necessary and vital, it can sometimes be detrimental when it comes to training Product Owners. Often the focus is purely on how the Product Owner can serve the team.
The Product Owner role is very different from the ScrumMaster role. It is a commercial function, more business focussed. It requires a different background, a different mindset and a different emphasis to teach well. This is why that for many years, the Scrum Alliance made it a requirement that in order to teach the CSPO, the instructor in question must have been a Product Owner for at least two years prior to teaching it. In order to meet increased demand for Product Owner training, this requirement has since been lifted.
Real World Product Ownership and Product Management Experience
Simon’s has a background in Business Analysis, Product Management, Project Management and of course Product Ownership. Pair this with an Executive MBA and this makes Simon the ideal choice to teach the CSPO certification. Simply put, he has a powerful combination of lived experience and formal qualifications.
The result is a course that focuses on the day to day reality of Product Ownership bringing a level of understanding and empathy that can sometimes be lost when the focus is on (and only on) how a theoretically perfect Product Owner should be.
A wide range of experiences in different industries
There is no one size fits all Agile. What’s appropriate for a start-up is not going to be suitable for an established enterprise or government agency. Simon has worked on everything from large military projects with budgets in the hundreds of millions using traditional and heavily regulated Waterfall methods such as 2167A and MIL-STD-498 And also to the surprise of many – Scrum!3
But equally he’s also worked for several start-ups discovering eXtreme Programming and Crystal along the way; later for incubators, government research labs, banks, airlines and non profit organisations.
He’s applied Scrum to hardware, software, analytics, data science & finance. He’s successfully dealt with multiple regulatory frameworks and environments. His most recent adventures have been in the heady of world of APRA Compliance Programmes.
Each of these new contexts has provided an opportunity for him to hone his craft and to get closer to the heart of Scrum, creating an ability to not just making it work, but work well, every single time.
Scrum is not just for small teams and simple projects. And it’s not just for software either. The beauty of Scrum is in how widely applicable the framework can be once you understand it deeply enough. Come and learn what’s possible.
Whilst the heart of Agile may well be “individual and interactions” the reality of today’s world is that we now live in a global business environment where even the simplest of projects can to live across multiple cultures and time zones. Over the last 25 years, Simon has worked throughout the UK, Australia, NZ, the USA, Europe, Scandinavia, Africa, the Middle East and Asia – programmes and portfolios of work involving three or more regions and time zones4.
Scaled Scrum Pioneer
Long before there were “Agile scaling frameworks” such as LeSS and SAFe – Simon along with his colleagues at Conchango (UK) was masterminding what we’d now call scaled and distributed Agile projects across Europe, Asia and America (sometimes all three!)
As part of this process, he quickly to learned that you’ve failed to scale agile until you’ve effectively scaled Product Ownership. And if you’re going to scale something, you better first understand how it works.
Scaling Product Ownership is a core part of scaling any agility to any meaningful level. Implementing Product Ownership poorly at scale hamstrings your ability to scale successfully (or indeed at all).
Scaling agile is very often done badly, becoming little more than “Waterfall with Stand Ups” or at the very least somewhat become deeply wasteful as it scales, dramatically reducing its effectiveness.
The worst way to scale anything is to learn it from a book. We suggest that you instead learn directly from the architect of some of the most successful scaled and distributed Agile Implementations on the planet. Scrum is fractal, it was meant to scale. And Scale Gracefully. Come learn how.
Decades of Hands on experience
When trainers and coaches talk about their agile experience they’re often exclusively talking about experience as a trainer or a coach. And whilst experienced trainers and coaches are undeniably a good thing, it’s still not the same as lived experience working inside a Scrum Team, or working as a Product Owner. Experience with genuine skin in the game, experience with all the inevitable trade offs, compromises and stakeholder demands that need to be met on a regular, sometimes daily basis.
Starting his Agile journey as a practitioner in the mid 1990’s, Simon is one of the most experienced, if not the most experienced coach, consultant or trainer currently working in Australia today.
When Ken Schwaber, original Agile Manifesto signatory, co-creator of Scrum and founder of the Scrum Alliance wanted to create a new Scrum Certification for the Scrum Alliance, who did he want on the team? Ken reached out to Simon Bennett and Colin Bird who were at the time both working for Conchango in the UK. Colin and Simon had previously worked with Ken on multiple previous occasions most famously on “Scrum for Team System” a Team Foundation Server (TFS) Process Template and associated Scrum Guidance.5
Simon was also invited by the Agile Alliance to sit on the Agile 2013 Stalwarts stage to speak to the topic of “Agile Contracting: A Systems Thinking perspective” alongside Jeff Sutherland, Ron Jeffries, Chet Hendrickson, Linda Rising, Steve Bell, James Newkirk and change management guru Linda Rising.
Thought Leader in Agile Contracting and Out Sourcing
Leveraging off his formal education in both Commercial Law and Game Theory, Simon has been working on “the problem” of Agile Contracting and Outsourcing since 2008, first publishing his work in the 6 out of 5 star rated workshop6 “The Prisoner’s Dilemma: Applying Game Theory to the Problem of Agile Contracting” at Agile 2009 in Chicago.
Since then, as an invited speaker, he has since spoken all over the world both publicly and privately on the topic of Agile Contracting and Outsourcing; alongside consulting on several high value outsourcing deals. (To both vendors and the clients)
His motivation has always been “how can we protect the interests of vendors and clients in a manner equal or better than a traditional contract does, whilst still retaining and maybe even amplifying the benefits of an Agile way of working” and after 10 years of mulling over the problem, he feels he’s pretty much cracked it.
Whilst agile contracting is still only a small part of the the industry, this way of working is slowly gaining traction. Too many people are still struggling in this area, believing that there are no answers! In today’s ever distributed and outsourced world, this work in what Simon now calls inter-organisational agility is becoming more relevant than ever.
He’s the Mindful Manager
The Agile manifesto begins with the declaration “…we have come to value… Individuals and Interactions” — since then the focus has mostly been on the interactions. Team work! Collaboration! Which is of course important.
In contrast to this, the Scrum Guide as well as a great many coaches and trainers, mandate that the Product Owner must be an individual and not a committee – and then places the weight of the world (or at least the work of 10 people) on their shoulders.
Product Ownership can be both mentally and emotionally taxing – after all it’s about making decisions, that have consequences. Again and again and again.
Ultimately the quality of these decisions are going to be affected by the emotional health and mental resilience of the person making them, which is why Simon has focussed so much in this area over the last 10 years.
Simon speaking publicly about this topic (Starting with The Perils of Prioritisation in 2012) as well as offering one on one coaching for Product Owners, especially in high pressure, high stakes environments. If you want people to bring their “whole selves” to work then you need to be prepared to deal with it.
“The Mindful Manager” has come to be Simon’s most popular talk in this genre, and in the last 5 years he has been invited to give it all over the world — often in conjunction with its companion workshop “Toyota Kata for the Mind”
Click here to see Simon presenting the Mindful Manager in Stockholm, opening for Al Gore (who sadly elected not to be recorded).
Our Training Philosophy
We believe the best kind of adult education is a solid mix of theory and practice.
At LASTing Benefits all our trainers were in the trenches practitioners before they became coaches, consultants and trainers. We believe this makes a difference, making our approach both pragmatic and transformative.
We’ve been in your shoes and broken every rule in the book – so we know what “mistakes”, compromises and Scrum Guide “violations” don’t actually matter and which ones you’ll really come to regret. Learn from our experience. We’ve got War Stories out the wazoo.
Whilst idealistic evangelical approaches to teaching Agile can be inspiring7, sometimes the practices can suddenly seem impossible once you’re back in the office. This can stall your agile adoption, leaving employees and customers alike feeling disappointed, grumpy and unfulfilled.
Equally, however, it has been out experience that overly pragmatic approaches to agile whilst flatteringly quick and easy to both understand and “roll out”, are too often deeply ineffective as they avoid addressing the real issues in favour of quick visible changes, which are only surface deep and ultimately ineffective.
We don’t believe in change for its own sake, nor do we believe in avoiding the elephant in the room in order to maintain the status quo and consultant billing hours up.
What we believe in is mindful considered change, the kind that leads to long lasting, effective, and meaningful results.
We believe in LASTing Benefits.
Come join us, we’d love to have you.
About LASTing Benefits
LASTing Benefits is a boutique consultancy founded over 11 years ago, with the core mission of enabling self sustaining agile transformations and adoptions.
Transformations that might start small, but are more than just surface deep, transformations that bring genuine and lasting benefits to an organisation, its employees and its customers.
To achieve this, we’ve mixed the Best of Agile with equal parts Lean and Systems Thinking then seasoned our approach with a healthy dose of cognitive neuroscience and social complexity. We accept your context and work within it.
We believe our courses have the perfect mix of theory of practice. Providing both Purpose and Practicality. We go beyond shallow tips and tricks to dig into the deeper layers of both the basics and “advanced” techniques alike.
Why settle for Agile when you could have LASTing Benefits?
- And if you don’t see yourself listed here but still feel like you’d like to come along, feel free to give us a call and talk about whether or not the LASTing Benefits CSPO is right for you! ↩
- No really! It is! Honest! ↩
- Back in the 90’s before people decided it was impossible. ↩
- Such as the clients in London, Front End developers in Shanghai and all the backend and integration work being performed in France by a 3rd party, using the strictest waterfall process imaginable. And yes, we learned a lot, and then made it work! ↩
- Between 2005 and 2010 the Scrum for Team System website maintained by Conchango was one of the authoritative source of Scrum knowledge globally. You can see Simon speaking on scaling scrum with v3 of Scrum for Team System here https://channel9.msdn.com/Events/PDC/PDC09/FT09 ↩
- Yes really! People drew an extra box on the feedback form just so they could rate the session 6 stars out of 5. ↩
- Or indeed off-putting. Everybody reacts differently. ↩