Generating options to change lose-lose contracts to win-win contracts and relationships, an #ExtremeContracts blog post

This is a guest blog post by Jacopo Romei. Author of the Italian version of the book Extreme Contracts, and author of an upcoming book on the same topic in English.

Contracts are usually designed around a unique way to deliver some effort, assuming there will only be one solution to the problem at issue.

This is wrong.

Not only conceiving more than one solution will enhance the chances to create a better one, but if we take into account some basic risk management principles, we may even help to shape a prosperous collaboration between us and our customers. In Extreme Contracts, we call this principle Optionality, and this is a story about how to see options where none seem to exist.

One problem, many solutions

Continue reading Generating options to change lose-lose contracts to win-win contracts and relationships, an #ExtremeContracts blog post

BONUS: Ash Maurya: Running Lean, Lean Product Development in practice

There’s many insights to be had from looking at how Startups and Lean Product businesses develop software and bring products to the market. In this BONUS episode with Ash Maurya, we learn about Lean Product Development from the author of Running Lean, one of the first published books around Lead Product Development.

Developing a book, the Lean way

Continue reading BONUS: Ash Maurya: Running Lean, Lean Product Development in practice

Nick Vitsinsky on how PO’s can prepare for meetings with the team

We explore the technical-dictator Product Owner anti-pattern and also talk about how great Product Owners get ready and come prepared for the meetings with the teams.

The Product Owner pattern for the week

When Product Owners come prepared to the meeting, you know they are doing their job well. They bring numbers, the rationale behind certain decisions, maybe even different options for priority to be chosen based on the feedback from the team. In this episode, we refer to the work by Jeff Patton and Jeff Gothelf, who’ve both been on the podcast before. You can find Jeff Patton’s Podcast episode here. You can find Jeff Gothelf’s podcast episode here.

The Product Owner anti-pattern for the week

Many Product Owners come from a technical background. This means that they know a lot about the technical aspects the team needs to consider. However, when the PO starts to question the team’s estimates or decisions, that’s a recipe for failure. Listen to how Nick handles that situation, and get some tools and practices you can apply right away!

 

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Nick Vitsinsky on The Island Expedition Agile Retrospective format

Is the team providing feedback openly to each other and stakeholders? That’s one of the key success questions that Nick asks when evaluating his own success as a Scrum Master.

That leads him to find approaches to help teams open up and share their perspective on the work.

In this episode, we also refer to a paper on how to help teams improve their performance. It is based on the same principle that top athletes apply every day: pushing, then resting. A cycle that is guaranteed to improve performance over time.

Featured Retrospective Format for the Week: The Island Expedition metaphor format

Nick likes to focus on creativity for the retrospectives he facilitates. He’s found several metaphor-focused formats that work, but one he especially likes is The Island Expedition.

Metaphor-focused formats help the teams be more creative by taking them out of their regular context and pushing them to imagine themselves in a different context.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Nick Vitsinsky: Top management support is not enough for Scrum adoption

Scrum Masters that move onto organizations that are just in the start of Scrum adoption may find that it is not an easy process, even when you have top-management support.

In this episode, we talk about what goes wrong when we focus on change from the top, and forget that the teams (whom we work with), might be against the change. Top management support is not enough for Scrum adoption!

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Nick Vitsinsky shares a common Scrum adoption Anti-pattern

When adopting Scrum, some organizations focus on the process, the meetings that come with Scrum. But, unfortunately, they also often forget about the meaning and the reason for those meetings, ending up just renaming the old meetings with new names.

This anti-pattern is common, and we should be able to detect it and counter it in our organizations. In this episode, we discuss how to detect and reverse the “same meetings with different names” Scrum adoption anti-pattern.

Featured Book of the Week: Management 3.0 by Jurgen Appelo

In Management 3.0 by Jurgen Appelo, Nick found a book filled with practical tips that help Scrum Masters (and managers) to work with the team every day, and make their work easier. In this episode, we also talk about the source for retrospective format ideas: Retromat.org; and about a book that inspires Nick every day: The Little Prince by Saint-Éxupery.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Nick Vitsinsky on the Scrum Master’s failure to motivate the team

Scrum Masters work with teams every day. The way teams feel about the work they do is extremely important for them to be engaged and motivated. However, sometimes we overlook that and fail. In this very personal story by Nick, we learn about what happens when Scrum Masters overlook and even ignore the motivation and engagement of the team.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Mili Shrivastava: When Product Owners can have multiple roles

We explore the absent Product Owner anti-pattern and discuss a case when it was OK to have the Product Owner also play the role of a developer in the team.

The Product Owner pattern for the week

We often hear that the Product Owner cannot be a developer at the same time. However, in some cases, that’s not a problem. In this episode, we talk about the Product Owner that was also a developer, and what made that PO a great PO despite the dual role.

The Product Owner anti-pattern for the week

When the Product Owner is too busy, the team suffers. In this episode, we talk about the anti-pattern of the absent Product Owner, and how Scrum Masters can help the team and the Product Owner in that situation.

 

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

Mili Shrivastava: Help your team be more effective with the KALM Agile Retrospective format

One of the most common, and sometimes forgotten, sensors for a Scrum Master is the daily meeting. Mili asks us to consider how the team members show up for the daily. Are they excited about the day that is starting? Or happy about the results of the day that is ending?

How are you using the Daily stand-up to assess your impact on the team?

Featured Retrospective Format for the Week: KALM

Keep your teams focused on the problems they want to solve with this simple format. KALM stands for Keep, Add, Less, More. These are the keywords that Mili asks the team to consider when reflecting on the previous Sprint.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

Mili Shrivastava: Helping Scrum teams improve their Sprint Planning

Planning for a Sprint is not an easy task. There are many unknowns, even at the Sprint level, and team members justifiably feel uncomfortable discussing commitments, when they know there will be unexpected events during the Sprint.

How can Scrum Masters help teams learn the value, and the mechanics of planning? That’s what we discuss in this episode.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn.