Agile fundamentals for teams

In this video, we’ll introduce the idea of a project and product mindset. We'll explore the differences between both approaches. Understanding this will help you choose the right approach for your context. Choosing the right approach can ensure better outcomes for both your team and your users. 

First, let’s talk about the project mindset. A project mindset is about working towards a specific goal. Most of the time, the aim is to deliver something within a defined timeframe. That means projects will usually have a clear beginning and end. Teams are often formed to deliver for the project. As a result, they tend to include people who don’t usually work together. This is because the skillsets needed may differ, depending on the nature of the project. 

A typical project moves through five phases: 

First is "Initiation". This is where the scope of the project and its objectives are set. 

Next, a team will begin "Planning". They will outline the steps, create a timeline, and identify the resources needed. The aim is to deliver something in scope, on time and within budget. 

A team will then begin to "Execute" the project. This is where they carry out what has been set out in the plan to achieve the objectives. 

Throughout this, they will be "Monitoring and Controlling" the project. The aim is to track progress and adjust as needed. These adjustments are likely to be very minor and are unlikely to stray too far from the initial plan. This is because it could have an impact on the scope, timelines or budget. Major changes would pose a high risk of a project failing. 

Finally, the project will "Close", once completed and the handover has taken place. The team will then usually disband. 

This works best when you have specific goal, limited timeframe, and fixed resources. For example, building something, like a community centre, would suit a project approach. The goal is clear and once built, the project ends. 

A project is a success if it delivers in scope, on time and in budget. But that doesn't guarantee the output will meet the needs of users. This could be because they've changed over time. There could be a shift in policy. Or technology may come along that offers new possibilities. These things cause a problem: 

the team hasn't had the chance to learn about these changes and adapt. This is particularly relevant in the context of delivering public sector services. The environment we're working is dynamic. Things change and teams need a way to deal with that. 

So, let’s look at a product mindset. A product mindset focuses on developing and improving a solution, over time. The goal isn’t to deliver something once. Instead, it's about identifying and solving problems. The aim is to meet the changing needs of users. It also enables teams to deal with changes to the context they are working in. 

With a product mindset, teams shift their focus to outcomes over outputs. Instead of delivering a fixed set of features, teams focus on delivering value to users. This often means adapting the solution as things change. Teams track success by how well it meets user needs and organisational goals over time. 

This approach is ideal when a product or service will need updates and improvements. For example, consider a digital product providing public health information and support. For this, a product mindset would be the best approach. It would need to change over time, based on user feedback and changing requirements. 

Later in the course, we'll look at how teams develop products and services, using this approach. 

To summarise, a project mindset is about completing a defined task within a set period. A product mindset focuses on delivering ongoing value. It achieves this by gathering feedback to improve a product over time. Both approaches have their place in public sector delivery. Understanding which approach to take, is critical to achieve successful outcomes.