The Importance of Professionalism

Summary

Martin Venture Woods, a professional Scrum trainer, discusses the significance of professionalism in software teams. He highlights that despite the initial aim of Scrum to create a unified set of rules, many teams fail to meet customer needs due to a lack of professional conduct and adherence to principles. Professional software delivery requires not only rules and engineering practices but, crucially, values like courage, focus, commitment, respect, and openness. With these in place, teams can deliver valuable and functional software consistently.

Highlights

• Scrum set the stage for professional behavior, but many teams missed the mark. 🎯
• Following rules is crucial - just like sticking to the game's rulebook! 📚
• Engineering practices are necessary, but without values, success is a mirage. 🌟
• Courage, focus, and commitment are the backbone of effective scrum teams. 💪
• Team respect fosters a harmonious and productive work environment. 🤝
• Openness ensures transparency and continuous improvement. 🔍

Key Takeaways

• Following rules can lead to unity and success, much like playing a board game with its rulebook! 🎲
• Good engineering practices, such as those in DevOps, contribute to software success. 🚀
• Values such as courage, focus, and commitment are vital to guide teams toward the right decisions. 🔑
• Respect within the team ensures all members are empowered and appreciated. ❤️
• Openness and transparency enable teams to adapt and improve continuously. 👁️‍🗨️

Overview

Martin Venture Woods dives into the core of professionalism within software teams. As a seasoned Scrum trainer, he points out how initially, the Scrum framework aimed to establish a common rule set to guide teams. However, in practice, many teams stray from these rules, leading to failure in meeting customer needs and undermining trust.

The solution isn't only about adhering to rules or engineering practices like those found in DevOps; it's about embodying vital values. Teams often neglect essential values such as courage, focus, and commitment, which are necessary to make the right choices and consistently deliver working software that satisfies customers.

Additionally, Martin emphasizes the need for mutual respect and openness within teams. These values foster a transparent, adaptable environment where everyone feels valued and heard. With these traits, alongside strong engineering practices, teams can consistently meet their delivery goals and exceed customer expectations.

Chapters

• 00:00 - 00:30: Introduction and Background The chapter "Introduction and Background" introduces Martin Venture Woods, a professional scrum trainer associated with 'Scrum Da Dark'. He is also a DevOps consultant and a Microsoft MVP. Martin extensively collaborates with software teams and shares his belief about what constitutes a professional software team.
• 00:30 - 01:00: Challenges in Meeting Customer Needs The chapter discusses the challenges faced by software development teams in consistently delivering working software that meets customer needs. Despite the widespread adoption of Agile and DevOps methodologies, many teams struggle to meet these expectations. This systemic issue leads to mass problems and a lack of trust in the industry. The chapter questions why Agile and DevOps are perceived to be failing and suggests that these methodologies may not be effectively implemented or aligned with true customer needs.
• 01:00 - 01:30: Importance of Following Rules The chapter emphasizes the importance of adhering to established rules within an organizational or team context. It begins by discussing the implementation of a set of rules, possibly through a methodology like Scrum, intended to align everyone in the same direction. However, it highlights a failure to follow these rules, attributing this lapse to a lack of professionalism. The key takeaway is that regardless of the practice or process chosen by an organization or team, it is essential to at least follow the established rules to ensure effectiveness and alignment.
• 01:30 - 02:00: Role of Engineering Practices The chapter discusses the role of having rules and engineering practices in a professional team. It starts by comparing the clarity provided by a rulebook in monopoly, although it may not help in winning. The emphasis is on the necessity of having rules for uniform direction and adherence to become professional. Additionally, the chapter points out the common failure among teams in implementing good engineering practices, which are crucial for team success.
• 02:00 - 02:30: Significance of Values and Principles The chapter discusses the importance of incorporating values and principles into software development, specifically highlighting the integration of DevOps practices as a means to enhance engineering capabilities. However, it posits that technical excellence and adherence to rules alone are insufficient for delivering effective and suitable software solutions. It identifies a crucial missing element beyond technology and practices that is essential for success in delivering the right software to customers.
• 02:30 - 03:00: Value: Courage The chapter titled 'Courage' discusses the importance of values and principles in an organization. It emphasizes that without these guiding principles, decision-making processes can falter, affecting the organization, its customers, and its teams. The primary focus is on the value of courage, highlighting it as essential for making tough decisions, such as saying no to customers when necessary. Courage is depicted as a foundational value that supports the integrity of decision-making within the organization.
• 03:00 - 03:30: Value: Focus The chapter titled 'Focus' emphasizes the necessity of courage and focus within a team, particularly in the context of agile project management. It underscores the importance of having the courage to take risks and make mistakes during a sprint, learn from them, and move on. Focus is highlighted as a critical element for guiding teams towards building the correct solutions, aligning with Sprint goals, and prioritizing the backlog appropriately to ensure everyone is working towards common objectives. Commitment as a team is also stressed as a key factor for achieving success.
• 03:30 - 04:00: Value: Commitment The chapter titled 'Commitment' emphasizes the collective and individual commitments necessary within a software development team and a scrum team. It highlights the product owner's responsibility to deliver maximum value to customers and underscores the importance of mutual commitments in the team to deliver working software. Additionally, the chapter stresses the need for organizational commitment to support the team in following processes and making the right decisions. It also calls for respect within the organization to foster a supportive environment.
• 04:00 - 04:30: Value: Respect The chapter titled 'Value: Respect' emphasizes the importance of respect within a team. It highlights that product owners should respect the team's efforts in building working software. Additionally, the chapter stresses the necessity of openness and transparency within the team environment. Openness is crucial for everyone to understand the backlog and what's happening, which enables the team to inspect and adapt accordingly. The discussion highlights respect and openness as essential values in agile product development, contributing to a collaborative and adaptive working environment.
• 04:30 - 05:00: Value: Openness and Conclusion The chapter titled 'Openness and Conclusion' emphasizes the importance of not just adhering to the rules but also integrating solid engineering practices. It stresses that the combination of these approaches enables the creation of software that consistently meets customer needs, highlighting a comprehensive approach to software development.

The Importance of Professionalism Transcription

• 00:00 - 00:30 my name is Martin venture woods I'm a professional scrum trainer with scrum da dark and also our DevOps consultant and Microsoft MVP and I work a lot with software teams and I found that what I believe to be true is that a professional software team is one that
• 00:30 - 01:00 can deliver working software on a regular cadence that meets their customers needs but what I've found in practice is that that is not the case and that most teams do not meet their customers need and they do not create working software and this is a systemic in our industry and causing massive problems and a lack of trust so we what have we been doing this wrong why why is agile failing for us why is DevOps failing forest fire all these failing for us and it's because we're not really
• 01:00 - 01:30 doing the right thing we kind of started with scrum so we created a set of rules with which and we can guide everybody in the same direction but what happened was that we didn't follow them we're not being professional at least following the rules whatever at practice or process you choose to do as an organization you choose to do as a team you should at least follow the rules if you bought
• 01:30 - 02:00 monopoly you would expect it to come with a rulebook not a strategy game and you would also expect that rulebook not to help you win they're playing the game just to help guide us all in the same direction so if you're going to have rules you should follow them that's the first thing that we need to do in order to be a professional team second thing we need is engineering practices this is another feeling of teams we fail to have good engineering practices now this is something that
• 02:00 - 02:30 should be easy to solve we just add continuous everything we bring devops into the mix DevOps has a set of practices that help us be better at engineering but even with those two things even with technical excellence and the rules we still don't deliver working software we don't deliver the right software to our customers and we failed to deliver working software because we're missing something crucial
• 02:30 - 03:00 we're missing values and principles without values and principles we don't guide ourselves to the right decisions at the right time within our organization for our customers and for our teams so what might those values be hopefully these are things that you want in your organization not things that you don't want we need courage courage is the first value we need courage to be able to say no to our customers we need
• 03:00 - 03:30 courage to be able to do the wrong thing for a sprint and for it not to go well to admit it make a change and move on so we need courage we need focus as well we need focus for our team to be able to go build something we need the focus of the Sprint goals so they're going in the right direction we need the focus of the backlog so that we're all building the right thing so focus is important we need commitment as a team our team our
• 03:30 - 04:00 software development team commit to delivering working software our product owner commits to delivering the most value to our customers these are all commitments that we need to make as a team and as a scrum team but our organization needs to commit to allowing us to do the right thing to follow the rules and the processes we also need respect within our organization we'd respect for
• 04:00 - 04:30 the product order that they're making decisions based on the knowledge they have the product owner needs to respect the team that are doing everything they can to build working software so respect is important too we need openness we need to be open with our with our backlog so everybody can see what's going on need openness to get transparency without transparency we can inspect and adapt so we need openness so those five things are in addition to our
• 04:30 - 05:00 engineering practices are in addition to just following the rules with all three of those things we're able to build working software that meets our customer needs on a regular cable [Music]