Beiträge

Veröffentlicht am

Why Good Product Management Matters: Key Indicators to Look For

Good product management decides about the success of a product and therefore often about the success of the total company. In the very beginning of a company, you mostly try to please just a few customers and they drive the change of the product. But as a company grows and customers pleasing everybody does not scale very well. Different customer groups do have different expectations on the product. Hence you need to make sure that your product evolves in the right direction pleasing the right lucrative customers. If you want to please everyone you will not deliver value for anyone in the long run.

At this point a good product management needs to take over to decide about the development of the product. Which part needs to grow, which parts needs to modernize, and which needs to be phased out. A product manager can take the decisions based on knowledge about various aspects of the product using multiple skills and technics. Seven very important aspects of good product management are mentioned in this article. Following these aspects will give a good start on the path to a good product management and concluding a good product.

1 Product managers know the goals of the company.

Product managers are responsible for their product. They make decisions about new features, modernization as well as removal of functionality. Any product decision needs to support the overall company goals. It can be the goal to gain new customers or to make a specific customer group happier by solving their specific problems. It can be a goal to reach a certain level of cloud compatibility or to make the customer onboarding process as easy as possible. Whatever the company goals are each product manager needs to know and internalize the goals. Product manager align the product development based on the goals and make sure to focus on achieving the goals. Additionally, product managers need to have the commitment that long term company goals are important enough to really work on them. Not aligning the product to the company goals and you will never achieve your goals, but instead have a bouquet of product features that do not match each other.

2 Product managers know the business of the company.

Product managers understand the economic value the company’s product create for the products users and the company itself. To be precise product managers need to know the amount of money the company makes by selling a specific part of the product. How much money does the company make by selling a specific module or feature set, how much does the customer pay to use a specific service. Without this knowledge the product management did not have the chance to produce value for the company. Instead, they create costly change that will not sell very well.

3 Product managers do know the products customer.

Knowing the customer is key knowledge for every product manager. You need to know the motivation to use your product and especially the problem your product solves and needs to solve in the future. Product managers need to experience the usage of their product as close from the real user as possible. In a business-to-business environment you also need to know the decision maker regarding the sales process of your software. Without knowledge of your customers problems, you will be trapped thinking within the solution space. Instead, you should think within the problem space of your customers. Product managers need to ask how the feature solves a problem for the customers.

Product managers find solutions for the problems customers and therefore allow every team member to create value working on the company’s product.

4 Product managers know the product.

A company’s product can be very complex. A lot of features, subproducts, modules, … have been created in the company’s history. Product managers need to be the expert when it comes to their team’s product and the company’s product. Without this knowledge the company will spend money on developing features twice or even three times. Additionally, you will develop features that customers already rejected in the past.

Using this product knowledge, product managers modernize and expand the product where necessary and refrain where possible.

5 Product managers make their decisions based on the market, competitors, and actual trends.

Product management does not happen in a happy bubble with no influence from the outside world. Instead, various factors from outside do need to influence the decision-making process regarding your company. It may be the competitor, that does have this one killer feature that your product is missing. Without the knowledge about this you will wonder why you do not sell your product well, but your competitor does.

Additionally, you need to know about the market. Which group of companies in the market do you currently address? What is the rest of the market and what will be needed to address their issues as well. Without this knowledge you will evolve your software, but nobody will need it, or you will try to please anybody because you do not understand that there is a market for your product.

6 Product managers communicate decisions about the product development.

Product managers make decisions daily. They decide which experiments to start, which feature to implement and very important which feature not to implement. Any decision regarding the direction a product evolves need to be transparent to the whole company. Your colleagues need to know why their requested feature has not been implemented they way they expected. Your developer needs to know about your decisions to implement it right. Product management is no ivory tower. Product managers need to tell the how and why of their decisions.

The transparency gained allows everybody to focus on achieving the product goals.

7 Product managers decide about the creation as well as the discontinuation of products.

When it comes to the new creation of a product the idea might come from any part of the company. But in the end, it is the product manager who need to decide if the new product will fit in the companies, customers, and market context.

High level managers tend to take the decision on their own and force the product manager to follow their way. Only the product manager does have the necessary background information.

Additionally, product managers decide about the end of live of a product. They know if there will be a valuable market in the future and if the product will stay maintainable.

8 Product managers know technics and tools

Decisions taken by a product manager need to be comprehensible and reliable. The best way to achieve this is using best practice techniques and tools to get all the data needed to understand product, market, competitors, and company. This way at least a sufficient number of decisions can be retraced later.

Product managers use data driven decisions to deal with the unexpected (e.g. experiments and agility).

Veröffentlicht am

The Road to Product-Led Success: Five Essential Steps

In the agile transformation organisations sometimes rely on implementing Scrum or some other agile frameworks. Scrum should make the company agile and customer centric. But the Scrum guide is incomplete by purpose. It only has a very limited set of tasks a product manager need to fulfil (Developing and explicitly communicating the Product Goal, Creating and clearly communicating Product Backlog items, Ordering Product Backlog items and Ensuring that the Product Backlog is transparent, visible and understood. [1]). How to create the product coal and any product backlog item refereeing to this goal is not part of scrum. This is where most companies get stuck in their agile transformation, as they tend to create the product goal and product strategy inside-out, top-down as usual. At this point, companies often wonder where the promised agility for success will lie.

Product led refers to growth strategy where the product is the primary driver of customer acquisition, engagement, and revenue. This approach prioritizes the user experience and focuses on building a product that is so valuable that it can drive customer acquisition and retention on its own, with less relying on traditional sales and marketing tactics. This approach is often used by software companies and can be contrasted with a traditional sales-led approach where the primary driver of growth is sales and marketing efforts.

Being product-led instead of sales-led brings some advantages for companies.

  • Cost-effective: Product-led growth relies on the product to drive customer acquisition and retention, which can be more cost-effective than traditional sales and marketing efforts.
  • Greater customer engagement: When the product is the primary driver of growth, it means that the company is focused on building a product that is valuable to the customer. This can lead to greater customer engagement and loyalty.
  • Data-driven: Product-led companies tend to be more data-driven, as they rely on data to understand how customers are using the product and to make informed decisions about product development.
  • Scalability: Product-led companies can scale more effectively as they rely lesss on salespeople to generate leads and close deals.

Overall, product-led companies tend to be more customer-centric, data-driven and scalable, while sales-led companies tend to be more sales-centric. Being product-led is clearly given advantages but the transformation is hard. In the following I describe some useful steps to become a more product-led company.

Product vision and strategy

Define your product vision and strategy: Clearly define what problem your product solves, who your target customer is, and what value it provides. If your strategy does not match your daily business or the daily business does not match your vision and strategy you are doing it wrong. A vision is not a set of actions, it is a clear goal what you want to achieve. This way anybody in the company is able to focus its work on reaching the goals.

Product people and manager need to sit down as long as it takes to have a product vision that is understood and supported by everyone.

Customer feedback

Prioritize customer feedback: Make sure you are gathering feedback from your customers on a regular basis and using it to inform product decisions. Do not try to define the needs of your software development inside-out. Only your customer knows what is needed.

Don’t be afraid. Go ask your customers what their biggest problem is you need to solve.

Product-focused culture

Build a product-focused culture: Ensure that everyone in the company understands the importance of the product and is working towards the same goals. Very often the different departments within the company (sales, consulting, marketing, …) do have very different goals in their daily work. Sales normally don’t care about being product centric. They need to sell whatever the next new customers need. Whether this is out of scope of your current product, or makes other customers unhappy is not important within the sales process.

Remove incentives on salespeople to sell more and more. Let them work instead to have the best product available on the market, to gain new customers.

Metrics

Focus on retention and growth: Measure the success of your product by looking at metrics such as customer retention and growth, rather than just acquisition.

Happy customers will lead to more customers. Make sure you have an idea what problems you need to solve for your customers need and how happy they are. This way you will easily get more customers.

Don’t stop!

Continuously improve and iterate: Use customer feedback, data, and testing to continuously improve and iterate on the product.

You are never finished with your product and you will never have ended to become even more product-led. Don’t stop taking the next step to get a better product.

[1] https://scrumguides.org/scrum-guide.html#product-owner

Veröffentlicht am

From Scepticism to Success: How to Get Buyers on Board for User Interviews in a B2B Setting.

In product management, understanding the customer is essential to creating a successful product. Conducting interviews is an excellent way to gain valuable insight into your customers’ needs, wants, and pain points. However, getting users to agree to an interview can be challenging. In this blog post, we will explore five steps you can take to make customer interviews happen.

Consumer vs. Business Products

In a business-to-consumer (B2C) business model, products are purchased and used directly by end-users. Examples include mobile apps, e-commerce websites, or video games. In the case of consumer products, user interviews tend to focus on understanding the user’s needs, wants, and pain points. The interviews are often designed to uncover how the user interacts with the product, what features they like or dislike, and what problems they encounter while using the product. In addition, product managers may also ask questions to gather feedback on potential new features or improvements that could be made to the product.

On the other hand, business-to-business (B2B) products are designed for use by companies rather than individual consumers. In this case, user interviews tend to focus more on understanding the business processes and workflows that the product is designed to support. The product manager may also seek to understand the decision-making process for purchasing products within the organization and the factors that influence that process. To achieve these goals, interviews may be conducted with individuals from different departments within the organization, such as finance, operations, or human resources, to understand their specific needs and pain points. For example: In B2B, the user and the buyer are usually different people, and product managers need to talk to both. They learn from users what makes a great product, and they learn from buyers what will sell in the marketplace.

But in addition to understanding their customers’ organizational structure, B2B product managers must also manage their internal stakeholders: Unlike in B2C companies, there is usually already someone in sales, consulting, or marketing whose job it is to talk to customers. This complicates things because they are an additional person that product managers need to bring on board. On the plus side, they usually have a good relationship with many potential interviewees, which makes it easier to get appointments.

So how do you navigate office politics, approach the customer, and make customer interviews happen?

Take advantage of internal knowledge first

When interviewing customers as a product manager, it’s important to remember that your own company likely has a wealth of internal knowledge that can inform your product decisions. Before looking to external sources, such as customers or industry experts, take advantage of the expertise within your own organization. This may include talking to other teams, such as customer support or sales, to learn about common pain points or frequently asked questions. Therefore, before interviewing customers, ask your customer-facing colleagues for their views on the market and the customer’s problem space. Not only do they work with real buyers every day, but they often have a great sense of the real problem you are solving. In many organizations, they are rarely asked for their input and get frustrated when the product does not reflect what they think the customer needs. So, you may lose their support by simply asking them for meetings with their accounts; ask them for their perspective first.

Make Sales, Consulting, and Marketing your allies.

Once you have a sense of your consultants’ and salespeople’s understanding of the market, customer, and product, explain the rationale behind customer interviews. Improve their understanding of the importance of product management in general and customer research in particular. Build confidence in your methodology. Make it clear that you want to help them sell more by giving them a better product. This alignment will increase their willingness to help you and will go a long way toward their later adoption of the resulting product strategy.

Handle resistance by taking small steps.

Despite your best efforts, you may encounter a team that is very protective of their customers and will not allow you to talk to them. As Teresa Torres writes, the key here is to take small steps to gradually reduce their fear of the unknown. For example: Ask if you can sit in on a sales meeting without saying anything, just observing. Then, at the next meeting, ask if you can ask a single question at the very end. And then iterate from there. Secondly, always look for ways to remove the risk from the situation. Who is the customer your sales rep would feel most comfortable reaching out to? Thirdly, help the salesperson adopt an experimental or prototyping mindset by framing the interview as an experiment rather than a long-term change. By working together, sales and product teams can create better products and improve customer satisfaction and by recognizing the importance of sales in customer relationships and collaborating effectively, product managers can help drive the success of their company’s products. https://www.producttalk.org/2022/05/sales-owns-customer-relationships/

Get an introduction to your interviewee.

The goal of our activities so far has been to get introduced to potential interviewees. We know from sales that such “warm outreach” is much more effective than getting in touch without a prior relationship (e.g., cold calling). A quick phone call from your sales rep may be enough to get you a meeting. So, whenever you have the opportunity, leverage the relationships your sales reps have built to get your interviews. This approach has the added benefit of aligning you with your sales team, which is essential in product management.

In a B2B context, building relationships and establishing trust is a critical aspect of securing interviews with potential customers or clients. This is because B2B transactions often involve larger sums of money and longer sales cycles than B2C transaction, which means that buyers are typically more cautious and risk averse.

When leveraging relationships with your sales team to secure interviews, it is important to ensure that your sales team has a strong understanding of your product or service and the value it provides to customers. This will help them to identify potential interviewees who are likely to be interested in speaking with you and who can provide valuable insights into the needs and preferences of your target market. When reaching out to potential interviewees directly, it’s important to take a personalized approach and tailor your outreach to their specific needs and interests.

However, if you fail and cannot get a meeting through sales, you will have to contact the customer yourself.

The cold case

In most companies, you have at least some customers who have had no contact with your company for a long time. These customers have never complained about anything and have never had the desire to get something new. However, these customers have a valid opinion about your product and you should really consider contacting them to get the full picture of your user and buyer group.

A common way to get in touch with these neglected buyers is by email. Email is a convenient way to reach out to potential buyers and schedule interviews. Emails are more likely to get a response than cold calls or unsolicited messages on social media. By crafting a thoughtful email that clearly explains why you are reaching out and how the buyer can benefit from participating in a interview, you can increase the likelihood of a positive response. If you send an interview request to somebody who did not expect it, you might not get an answer very often. Here is some advice on how to write the email so that you get as many responses as possible.

Be short: Your cold email is very likely not the only email your interviewee will receive that day. By writing a short email, you show that you respect their time and prioritize their attention. Also, a short email is much more likely to get attention, and this will more often lead to a possible response, as people are more likely to respond to emails that are easy to read and respond to. If your email is long and verbose, the user may not bother to respond. Your rule should be to write between 5–7 sentences only. More and the recipient will likely not even read your message to the end.

Furthermore, a short email forces you to make your message clear and understandable. This is especially important in a cold email, where the user may not be familiar with you.

Personalize your message: Address the customer by name and tailor your message to their specific needs or pain points. Try to communicate why you are reaching out to this recipient. Leverage their previous interactions with your company. If your respondent has the slightest feeling that they are being contacted by a bulk email or even a bot, the chances of you getting a response are close to zero.

Address your customers vanity: If you can really make the recipient feel special, they will most likely help you get the interview you want. Try to address their vanity by telling them why you need them. Be eager to tell them that they may be the experts on the product you want to improve. Tell them that their opinions and expertise are valuable to you.

Do not try to sell anything: The last time someone contacted your potential interviewee, it was to sell something. If your email recipient gets the feeling that you contacted them just to make money, they may not send you a response, or worse, they may not answer honestly, making your whole interview useless. Tell them that your intention is to improve the product and that you are not interested in selling them anything.

Include a clear call-to-action: Tell the customer exactly what you want them to do next, whether it’s scheduling a call with you, signing up for a free trial, or responding to your email with feedback. Make it easy for the customer to act by including links or buttons to relevant pages on your website.

In conclusion, conducting interviews in a B2B setting is an essential step in improving your product strategy and building stronger relationships with your buyers. Whether you’re reaching out to people in close contact or conducting cold email interviews, there are several key steps you can take to secure valuable feedback and make the most of the interview process.

First, take all internal resources into account to get a good understanding of who your customers are and what their intent is in purchasing your product. Your internal stakeholders, as well as your customer, need to understand why you’re reaching out to the buyers and how they can benefit from participating in the interview. This can help establish trust and increase the likelihood of a positive response.

When cold emailing, it’s important to keep your message concise and to the point. Respect the buyer’s time and deliver your message clearly and concisely. This can help increase the likelihood of a response and encourage thoughtful engagement.

Overall, conducting customer interviews in a B2B environment requires careful planning, preparation, and execution. By following these essential steps, you can secure valuable feedback, build stronger relationships with your buyers, and improve your product strategy for long-term success.

Veröffentlicht am

Enhancing Agile Team Collaboration: Techniques for a Medium-Size Software Product Development Company

Collaboration is the beating heart of Agile methodologies, and it holds the key to success for medium-sized software product development companies. In this blog post, we will delve into techniques that can enhance team collaboration within this specific context. By focusing on effective communication, cross-functional collaboration, fostering a culture of trust, and creating an environment that encourages knowledge sharing and innovation, we can optimize collaboration and propel our Agile projects towards unparalleled success.

Effective Communication

Clear and open communication is the cornerstone of fostering collaboration. As a Scrum Master, it is essential to encourage regular team meetings, such as daily stand-ups, to keep everyone informed about project progress, challenges, and goals. Emphasize the importance of active listening and create a safe space for team members to express their ideas and concerns. To facilitate effective communication, make use of digital collaboration tools that can enhance interactions, facilitate virtual collaboration if needed, and ensure that all team members have equal access to necessary information and resources.

Cross-Functional Collaboration

In medium-sized software product development companies, cross-functional collaboration is paramount. Encourage interaction and knowledge sharing among different teams and departments. Foster a collaborative mindset that transcends individual roles and promotes a shared understanding of project goals. Conduct workshops and brainstorming sessions to encourage diverse perspectives, problem-solving, and innovation. By breaking down silos and promoting collaboration across disciplines, teams can leverage the collective expertise and creativity of the entire organization.

Fostering a Culture of Trust

Trust forms the foundation of effective collaboration. As a Scrum Master, it is crucial to foster a culture of trust by promoting transparency, accountability, and psychological safety within the team. Encourage team members to share their ideas, insights, and concerns without fear of judgment or repercussions. Lead by example, demonstrating trustworthiness, and encourage collaboration over competition. Celebrate individual and team achievements, and provide constructive feedback to support growth and improvement. By nurturing trust, you create an environment where collaboration can flourish.

Creating an Environment for Knowledge Sharing

Knowledge sharing is vital for continuous improvement and innovation. Encourage the use of collaborative platforms, such as wikis or internal knowledge bases, to document and share project-related information, best practices, and lessons learned. Organize regular knowledge-sharing sessions where team members can present their expertise or share new technologies and approaches. Create opportunities for mentoring and coaching, allowing team members to learn from each other and develop their skills. By fostering a culture of knowledge sharing, you promote a learning organization that thrives on collaboration and continuous growth.

In conclusion, effective collaboration is indispensable for the success of Agile methodologies in medium-sized software product development companies. By implementing techniques such as effective communication, cross-functional collaboration, fostering a culture of trust, and creating an environment for knowledge sharing, Scrum Masters can elevate team collaboration to new heights. Embracing collaboration as a core value and nurturing an environment that supports it leads to increased productivity, enhanced problem-solving capabilities, and the ability to deliver high-quality products. By continuously improving collaboration practices, we can unlock the full potential of Agile methodologies and drive our projects towards even greater success.

Veröffentlicht am

Focusing on Quality Attributes for Superior Software Delivery

Agile software development is a methodology that emphasizes on iterative and incremental development, frequent inspection, and adaptation. It focuses on delivering working software frequently, responding to changes in requirements, and collaborating with the customer throughout the development process.

The main purpose of agile is delivering and exchange value with customers. Mostly value is associated with features. This is what customer will ask for and this is what customers will notice. Everything else such as reliability, maintainability, scalability, performance, security, and usability just needs to be build in. These aspects of software will only be notice if absent and a problem occurs. Therefore, we must make sure that the implementation of soft aspects is part of software development. However, developing software with agile methodology does not guarantee the quality of the software. Therefore, it is important to pay attention to quality attributes in agile software development. In this blog post, we will discuss how to achieve quality attributes in agile software development.

What are quality attributes?

Quality attributes are the non-functional requirements of a software system. They are the characteristics that define the quality of the software, such as reliability, maintainability, scalability, performance, security, and usability. These attributes are essential for the success of the software system, as they determine how well the software meets the needs of the users.

ISO/IEC 25000 is a standard that provides guidelines for software quality requirements and evaluation. It is also known as the Software Product Quality Requirements and Evaluation (SQuaRE) standard. The standard describes a framework for evaluating the quality of software products based on eight quality characteristics, which are:

  • Functionality: The degree to which the software satisfies specified requirements.
  • Reliability: The ability of the software to perform its required functions under stated conditions for a specified period.
  • Usability: The degree to which the software is easy to learn, understand, and use.
  • Efficiency: The degree to which the software performs its functions with appropriate speed and resource utilization.
  • Maintainability: The ability of the software to be modified or enhanced easily and effectively.
  • Portability: The ability of the software to be transferred from one environment to another.
  • Compatibility: The degree to which the software can operate with other software, hardware, and systems.
  • Security: The degree to which the software protects against unauthorized access, use, disclosure, disruption, modification, or destruction.
Es wurde kein Alt-Text für dieses Bild angegeben.

Developing software that meets the quality attributes outlined in ISO/IEC 25000 can be a challenging task, particularly when using an agile development approach. However, with careful planning, attention to detail, and a focus on quality throughout the development process, it is possible to achieve a high-quality software product that meets or exceeds the expectations of its users.

Here are some key steps to follow when developing software using an agile approach that meets the quality attributes outlined in ISO/IEC 25000:

Define and prioritize quality attributes: Before starting the development process, it’s essential to define and prioritize the quality attributes that are most important for the software product. This involves working closely with stakeholders to understand their needs and expectations, and using this information to determine which quality attributes are most critical.

Prioritising quality attributes especially involves deciding whether to develop another feature or spend time on security, reliability, etc.

Incorporate quality throughout the development process: One of the key principles of agile development is to prioritize quality throughout the development process. This means incorporating testing, code reviews, and other quality control measures into each stage of the development process, rather than treating it as an afterthought.

Use iterative development: Iterative development is a key part of the agile methodology, and it can be particularly useful when working to meet quality attributes. By breaking down the development process into smaller, manageable iterations, it becomes easier to focus on quality at each stage, identify and address issues quickly, and make improvements as needed.

Conduct frequent testing: Testing is a critical part of the development process when working to achieve high-quality software. Agile development emphasizes frequent testing, which allows for issues to be identified and addressed quickly, reducing the risk of defects, and ensuring that the software meets quality standards.

Embrace continuous integration and delivery: Continuous integration and delivery (CI/CD) is another key aspect of agile development, and it can be particularly useful when working to meet quality attributes. By automating the build, test, and deployment process, it becomes easier to identify and address issues quickly, reduce the risk of defects, and ensure that the software meets quality standards.

Monitor and measure quality: Once the software product is released, it’s essential to monitor and measure its quality to ensure that it continues to meet the standards outlined in ISO/IEC 25000. This involves collecting data on key quality metrics, analysing this data to identify areas where improvements can be made, and using this information to guide future development efforts.

In conclusion, developing software that meets the quality attributes outlined requires a concerted effort to prioritize quality throughout the development process. By working closely with stakeholders, incorporating quality control measures at each stage of the development process, and embracing the principles of agile development, it’s possible to achieve a high-quality software product that meets or exceeds the expectations of its users.

Veröffentlicht am

Scrum Masters are true leaders

The Scrum Guide defines the Scrum Master role as a “servant-leader for the Scrum Team,” responsible for promoting and supporting Scrum by helping everyone understand the theory, practices, rules, and values. The Scrum Master is also tasked with removing impediments and helping the team become self-organized and high performing.

When the Scrum Guide says that Scrum Masters are “true leaders,” it means that the role requires the ability to lead without formal authority, by empowering and enabling the team to achieve its goals. This leadership approach is often referred to as servant-leadership, where the leader’s focus is on serving the team’s needs and removing obstacles, rather than issuing commands or directives.

Pros and cons

Some of the pros of having Scrum Masters as true leaders include:

· Improved collaboration: The servant-leadership approach of Scrum Masters can help create a collaborative environment where team members feel empowered and valued. This can lead to better communication and cooperation between team members.

· Increased team motivation: When Scrum Masters empower their teams to take ownership of their work and decision-making, team members may feel more motivated to achieve their goals and deliver high-quality work.

· Greater adaptability: By removing impediments and helping the team become self-organized, Scrum Masters can create a more flexible and adaptable team that can quickly respond to changes and challenges.

However, there are also potential cons to having Scrum Masters as true leaders:

· Lack of experience: Scrum Masters may not have the same level of technical or domain-specific knowledge as other team members. This may make it difficult for them to understand and help solve certain technical problems.

· Conflict of interest: As Scrum Masters are responsible for both the team’s success and adherence to Scrum principles, there may be situations where these two goals conflict. For example, if a team member is not adhering to Scrum principles, the Scrum Master may need to hold them accountable, which could harm team cohesion.

· Difficult to balance responsibilities: The Scrum Master role can be challenging, as it requires balancing multiple responsibilities such as facilitating meetings, coaching team members, and removing impediments. This can be difficult to manage and may lead to burnout.

Overall, having Scrum Masters as true leaders can have significant benefits for a Scrum Team, but it also requires a specific leadership approach and a balance of responsibilities. It’s important to consider the pros and cons before assigning someone to the Scrum Master role and providing them with the appropriate training and support to ensure success.

Becoming a true leader

To become a true leader as a Scrum Master, there are several steps you can take to develop the necessary skills and qualities. Here are five important steps to consider:

1. Understand Scrum principles and values: A true Scrum Master should have a deep understanding of the Scrum framework, its values, and principles. This means taking the time to learn about Scrum, attending training, and staying up to date with the latest changes and updates.

2. Develop strong communication skills: As a Scrum Master, you will need to be an effective communicator, able to listen actively, ask the right questions, and provide clear and concise feedback. This includes facilitating meetings, resolving conflicts, and coaching team members on best practices.

3. Practice servant-leadership: The role of a Scrum Master is to serve the team, not to manage or control them. To become a true leader, you should adopt a servant-leadership approach, putting the needs of the team first and supporting them in achieving their goals.

4. Foster a culture of continuous improvement: As a Scrum Master, you should encourage the team to continuously improve and learn from their experiences. This means providing opportunities for retrospectives, encouraging feedback, and helping the team identify areas for improvement.

5. Develop a growth mindset: To become a true leader, it’s essential to have a growth mindset, which means embracing challenges and seeing failures as opportunities for learning and growth. This mindset will help you stay positive and focused on continuous improvement, both for yourself and the team.

In summary, becoming a true leader as a Scrum Master requires a combination of technical knowledge, soft skills, and leadership qualities. By following these five steps, you can develop the necessary skills and mindset to empower your team and facilitate successful Scrum projects.

Veröffentlicht am

Metrics for the transformation to Product-First

In product development, organizations are increasingly shifting their focus from a service-oriented approach to a product-first mindset. This strategic transition involves prioritizing the enhancement and innovation of newer products, while limiting investments in legacy offerings. To gauge the success of such a transformation, it becomes crucial to track key metrics that provide insights into the effectiveness of the product-first approach. In this article, we delve into two essential metrics-developer time spent on old products and the number of tickets related to legacy offerings-as powerful indicators of progress towards a product-centric strategy. Let’s explore how these metrics can help evaluate and drive the effectiveness of your organization’s product-first approach.

At its core, the product-first approach centres around delivering exceptional value by focusing on features and improvements that truly elevate the product’s quality and user experience. It involves a deliberate decision not to implement every customer request, but instead to invest in those that contribute to making the product great. By waiting for a critical mass of customer demand before introducing new features, organizations can optimize their resources and prioritize development efforts to align with market needs. Furthermore, self-service options are embraced to empower customers, reducing reliance on extensive consulting and support.

Assessing Developer Time Spent on Old Products

One key metric for evaluating the success of a product-first approach is the time developers spend on old products. By tracking and analysing the allocation of developer resources, organizations can gain insights into their focus and priorities. A reduction in the time dedicated to maintaining and supporting legacy offerings indicates a successful transition towards prioritizing newer products. This shift signifies a commitment to innovation, as resources are redirected towards enhancing the quality, functionality, and overall value of flagship products. Ultimately, it enables organizations to respond more swiftly to market demands, fostering greater customer satisfaction and a competitive edge. When organizations reduce the time spent on old products, it signifies a fundamental change in their development mindset. It reflects a strategic decision to shift the balance from maintaining outdated solutions towards investing in the continuous improvement of newer offerings. By dedicating more resources and time to enhancing these products, teams can drive innovation, respond to market trends more effectively, and deliver enhanced value to customers. This shift also cultivates a culture of agility and adaptability, enabling organizations to stay ahead in rapidly evolving markets.

Leveraging the Number of Tickets on Old Products

Another essential metric for evaluating the success of the product-first approach is the number of tickets associated with legacy products. Fewer tickets indicate a reduced need for support and maintenance on older offerings. By effectively addressing and resolving customer issues, organizations can minimize the number of tickets generated, freeing up valuable resources. This reduction allows teams to focus their energy on product innovation, accelerating development cycles, and improving time-to-market. Ultimately, it paves the way for more efficient and streamlined operations, resulting in greater customer satisfaction and improved overall product performance.

Regular monitoring of these metrics is essential to evaluate the long-term impact of the product-first approach, identify areas for improvement, and adapt strategies accordingly.

Product Abandonment

In addition to tracking developer time and tickets, another crucial factor to consider when evaluating the success of a product-first approach is the customer base using old non-strategic products. The number of customers relying on outdated offerings can significantly impact resource allocation and priorities. If a substantial portion of customers still utilizes legacy products, the need for support, bug fixing, and maintenance will persist. In such cases, it becomes essential to dedicate the necessary time and resources to ensure customer satisfaction and minimize disruptions.

Conversely, as the customer base transitions towards adopting the newer products within the portfolio, organizations can allocate more time and attention to strategic products. With a reduced reliance on outdated solutions, development teams can channel their efforts into enhancing the functionality, usability, and competitive advantage of the newer offerings. This shift enables organizations to capitalize on market trends, drive innovation, and deliver greater value to their customers.

By carefully monitoring the customer base and understanding the adoption rates of newer products, organizations can make informed decisions about resource allocation, development priorities, and support strategies. This customer-centric approach ensures that efforts align with market demand, maximizing the potential for success in the product-first journey.

In summary, the composition of the customer base and the adoption rates of products play a pivotal role in determining the allocation of resources and time. A higher number of customers using outdated non-strategic products may necessitate increased support and bug fixing efforts, while a growing base of customers embracing newer offerings empowers organizations to focus on the strategic products that drive innovation and differentiation in the market. Balancing these factors is vital for effectively implementing a product-first approach and achieving sustained success.

Release Age Metrics in Product Management

In addition to the metrics mentioned earlier, another valuable metric to consider when evaluating the success of a product-first approach is the age of releases in production. The age of a release refers to the time elapsed since its deployment to customers. This metric provides insights into how effectively organizations are encouraging their customers to adopt new releases and stay up to date with the latest product enhancements.

When customers tend to use older releases for extended periods, it can result in increased support and bug fixing efforts. Timely resolutions for issues and customer requests become necessary to ensure customer satisfaction and minimize any potential disruptions caused by outdated versions. This situation can strain development resources and hinder progress towards a product-first mindset.

Conversely, if product management can successfully persuade customers to update frequently and adopt new releases promptly, it can yield significant benefits. By encouraging customers to stay current, organizations can save valuable time and resources that would have otherwise been spent on supporting and maintaining multiple outdated versions. Additionally, frequent updates enable organizations to deliver new features, improvements, and bug fixes more efficiently, providing enhanced value and addressing customer needs more effectively.

Relating these metrics to the well-known DORA (DevOps Research and Assessment) metrics, which focus on key performance indicators for high-performing software delivery teams, there are notable connections. The DORA metrics, such as deployment frequency, lead time, change failure rate, and mean time to recovery, align with the goals of a product-first approach. By promoting frequent updates and reducing the age of releases, organizations can improve their deployment frequency, reduce lead time, and lower the change failure rate. Additionally, faster recovery times from incidents or issues in newer releases can be achieved through improved monitoring and bug fixing processes.

In the context of product management, these metrics help measure success by assessing the organization’s ability to deliver value, respond to customer needs, and maintain a rapid feedback loop. By tracking the age of releases and analysing its impact on support, bug fixing, and customer satisfaction, organizations can identify areas for improvement, establish targets for timely updates, and measure progress towards achieving a product-first approach. These metrics serve as a valuable tool for product managers to drive continuous improvement, optimize resource allocation, and align development efforts with customer demands.

The age of releases in production is a significant metric that reflects the effectiveness of product management in encouraging customers to adopt new versions promptly. By reducing the reliance on outdated releases, organizations can save time and resources while delivering value through frequent updates. These metrics, when aligned with the DORA metrics, contribute to measuring success in product management by evaluating the organization’s ability to drive innovation, agility, and customer satisfaction through a product-first approach.

Milestones

Es wurde kein Alt-Text für dieses Bild angegeben.

Using milestones in the form of thresholds can be highly beneficial when evaluating the success of the product-first approach. These milestones serve as specific targets or goals that provide a clear direction for progress and enable product managers to track the effectiveness of their strategies.

By setting thresholds for metrics such as Developer Time, Number of Tickets, Customer Adoption (%), and Deployment Frequency, organizations establish actionable milestones to measure their performance against. These thresholds can be based on industry benchmarks, internal goals, or historical data. They act as guiding points, helping product managers gauge progress and make informed decisions regarding resource allocation and strategy adjustments.

The inclusion of milestones in the comparison table brings several advantages. Firstly, they provide a tangible way to assess progress and success. By comparing the actual metric values against the predefined thresholds, organizations can easily determine whether they are on track or if adjustments are necessary.

Secondly, milestones offer a sense of direction and motivation. They provide clear targets for teams to work towards, fostering a shared understanding of the desired outcomes and creating a sense of purpose. As each milestone is achieved, it becomes a cause for celebration and reinforces the product-first mindset within the organization.

Furthermore, milestones enhance communication and alignment. By having predefined thresholds, product managers can effectively communicate expectations and progress to stakeholders, such as executives, development teams, and customers. It facilitates transparency and ensures that everyone is working towards the same goals.

Lastly, milestones enable the identification of areas for improvement. If a metric falls below the threshold, it serves as an early warning sign, indicating the need for corrective actions. Conversely, surpassing a milestone can signal success and provide valuable insights into the effectiveness of the strategies employed.

By diligently monitoring and analysing these metrics, product managers can assess the effectiveness of their product-first approach and make data-driven decisions. Successfully implementing a product-first strategy results in optimized resource allocation, improved customer satisfaction, and a competitive advantage in rapidly evolving markets. Embracing these metrics as indicators of success empowers organizations to continuously improve their product management practices, innovate proactively, and deliver exceptional products that meet and exceed customer expectations.