Viewing Posts by Sree Rao
How to Create Effective Exit Criteria
Categories:
Program Management
Categories: Program Management
By Sree Rao, PMP, PgMP, PMI-ACP
“Begin with the end in mind” is one of the recommendations from The 7 Habits of Highly Effective People by Stephen Covey. Extending that to program management, “Begin with exit criteria” should be one of the habits of an effective program manager. Exit criteria are the specific conditions that must be met before a program/project can be considered complete. Defining exit criteria is one of the most critical aspects of ensuring a successful product, feature or project launch. Exit criteria depend on the type of the program. For example, construction projects would have different criteria from software programs. My experience is in software development, and so the examples and insights I share in this post are about software programs. I will discuss the importance of defining exit criteria and share some tips on how to create effective ones. Importance of Exit CriteriaExit criteria are a set of predefined conditions that serve as the benchmark for determining whether a feature is ready to be deployed to meet user needs and quality standards. Exit criteria can be set at various phases of a program, like going from the quality assurance phase to user acceptance testing. By establishing these criteria early in the development process, teams can ensure that everyone involved in the project shares a common understanding of what leads to a successful outcome. This alignment helps prevent misunderstandings or miscommunications that could lead to program delays. Clear exit criteria also promote accountability among team members. When each person knows exactly what is expected of them in terms of deliverables and quality standards, they can work more efficiently. Additionally, having well-defined exit criteria allows teams to track progress more accurately and identify potential issues earlier in the development cycle, making it easier to course correct if necessary. Creating Effective Exit CriteriaDetermining the exit criteria depends on the type of program and the goals of the program. If it is a new feature development, then the exit criteria would be dependent on the success criteria for that feature. If it is a program to reduce bugs across the team, exit criteria would be different. The best way to come up with exit criteria would be to think about what success would look like for that feature and then create exit criteria accordingly. Here is how to create effective exit criteria:
|
Exit Criteria | Priority | Confidence Level |
Customer satisfaction (CSAT) score of >4 (out of 5) | High | High |
Response time of 2-3 seconds for 95% of users | High | Medium |
No high severity issues before launching to users | High | Low |
Conclusion
Defining exit criteria is an important aspect of managing a successful program launch. I ran some programs without aligning on exit criteria at the beginning of the program and had to scramble toward the end, which caused a lot of stress—and in some cases program delays as well.
By setting clear, measurable and collaborative criteria, you can ensure that your team is aligned and working toward a common goal. Remember that exit criteria should prioritize user needs; balance quality and time constraints; and be regularly reviewed and updated throughout the development process. By following these guidelines, you can significantly increase the likelihood of a smooth and successful program launch.
3 Valuable PM Lessons I Learned in 2023
By Sree Rao, PMP, PgMP, PMI-ACP We are almost at the end of 2023! As I take a moment to reflect on this wild ride of a year, here are three key lessons I learned that I wanted to share with you all. 1. Embrace change: Projects are like a box of chocolates…you never know which ones might get canceled. It was super demotivating. But as technology continues to evolve, customer needs shift and market trends change, it's essential to stay flexible and change course as strategy demands. If you ever have to deal with such a situation, rather than feeling demotivated you should embrace it as an opportunity for growth and learning. By doing so, you'll be better equipped to lead your team through the ups and downs. One of my mentors gave this perspective, which has helped me immensely: “We get paid to do the work without promises that the features/projects will be released to production. So as long as you get paid and you are continuing to learn, do your best work and leave the rest.”
What I realized is that we can pursue our interests in other ways and means instead of completely switching careers or trying to turn hobbies into a living. We can pursue our passions/interests in small ways like finding opportunities in the domain that we are interested in. As an example, if your hobby is photography and photo editing, perhaps you could continue being a program manager but find a job in a company that specializes in photo editing software like Adobe. Find the domain or area that brings you joy—whether it's event management, innovation or team building—and find opportunities in that domain. When you enjoy what you do, everyone benefits—not just your own well-being, but also your program's success.
As a program manager, we have the privilege of working with talented team members who contribute their skills and expertise to our projects. Rather than thinking “they are doing their job,” make it a point to express gratitude toward them regularly. A simple "thank you" or acknowledgement can go a long way in building positive relationships within your team By embracing these three lessons, you'll be better equipped to navigate the challenges of program management in 2024 and beyond. Remember, as a program manager, our role goes beyond managing projects; it's about leading people, fostering collaboration and driving impactful results. As we bid farewell to another year, I want to express my heartfelt gratitude to each and every one of you for your thoughtful comments and engagement. (A special shoutout to our editor Cameron for inspiring me to write and for shaping my musings a better way). Wishing you all a blessed 2024! |
The Importance of Strategic Management for Technical Program Managers
By Sree Rao, PMP, PgMP, PMI-ACP During my initial phases as a technical program manager, I was heavily focused on the execution of programs and didn’t bother much with strategy. As I gained more experience, I realized the importance of understanding strategy and how it can uplevel us as program managers. Based on my experience, there is a common misconception that TPMs only play a role in program execution once a strategy has been determined. Strategy plays a crucial role in determining the success of any program, so in this post I will discuss why being plugged into strategy is essential for TPMs. Strategy vs Plan: Understanding the Differences What is Strategic Management? One of the key benefits of strategic management is its ability to provide a clear roadmap for achieving project/program goals. Strategy involves conducting market research, analyzing competitive landscapes, identifying customer needs, and developing long-term plans that align with business objectives. By having a well-defined strategy in place, we can ensure that our projects are focused on delivering value to stakeholders—while also contributing toward the organization's overall success. Product managers usually create the strategy, but TPMs play a significant part in putting it into action. Why is Strategic Management Important for TPMs?
Conclusion Disclaimer: My experience has been only in the tech industry, and I am not sure if this is prevalent in other industries. I would love to know if you have experienced something similar.
|
Task Conflict vs. Relationship Conflict
As program managers, we have to deal with various conflicts in the workplace. The book Think Again: The Power of Knowing What You Don't Know by Adam Grant calls out valuable insights into distinguishing between task conflicts and relationship conflicts—and this proves useful in reaching effective resolutions. According to Grant, task conflict refers to disagreements or differences of opinion that arise between team members regarding the tasks they are working on. On the other hand, relationship conflict refers to personal disagreements or clashes between team members that are not related to the tasks they are working on. Relationship conflict could be due to power struggles, personality conflicts or prior conflicts leading to mistrust. Task Conflict By having diverse opinions and having team members debate various options, we get an exploration of ideas and solutions. Task conflict often stimulates healthy debate and increases team motivation, as team members feel that their input is valued. Grant states that some organizations build challenge networks (groups of thoughtful critics) into their cultures to stir up task conflict. If your team does not have task conflicts, it might be a sign of lack of trust or other underlying issues. While task conflict is beneficial, it is important to manage it properly. As program managers, we can play a crucial role in resolving task conflict by implementing the following strategies:
Relationship Conflict Occasionally, relationship conflict can manifest as task conflict. If you notice that the same individuals have recurring task conflicts even when it is not necessary, it should signal that there are some underlying relationship issues. I have noticed this a few times with a few of my team members—and upon further investigation, I was able to find that the individuals in question had relationship conflict. Here are a few tips for dealing with relationship conflicts:
While it is not possible to avoid relationship conflict completely at work, you can minimize them. One way to keep relationship conflicts to a minimum is by creating professional boundaries at work and not oversharing your personal information. Getting too involved in others’ personal issues or oversharing your personal information can create unnecessary emotional investment and conflict. I have had my share of conflicts as well—and wondered why I felt uncomfortable dealing with some conflicts versus others. This insight about task versus relationship conflict helped me figure out the reason why. In conclusion, I can attest to the importance of understanding the differences between task and relationship conflict. While task conflict can be constructive if managed properly, relationship conflict is often detrimental. By understanding these differences, we can better manage conflicts and create a more positive, productive environment for everyone involved. What strategies have you found to be most effective in resolving conflicts? Leave your ideas in the comments below! |
10 Key Lessons From 10 Years of Program Management
By Sree Rao, PMP, PgMP, PMI-ACP From rookie mistakes to hard-won victories, my decade-plus journey as a program manager has been full of lessons. Here are the ones that stuck with me the most. As you ring in 2023, I hope these lessons will help you on your PM journey. 1. Don’t get too caught up in processes and labels. In my early career as a PM, I was stuck on implementing agile methodologies like scrum, Kanban etc. With experience, I have come to realize that it is important to figure out a process that works in the team-specific context rather than sticking to the labels of agile versus waterfall. What is effective for one team might or might not work for another team. We get better engagement and buy-in if we involve the team in setting up processes and make the changes that the team recommends. It is important to rely on the collective wisdom of the team. 2. Don’t try to control the outcome of meetings. I place a high value on clear agendas and sticking to them in meetings. However, there have been occasions where my meetings did not go as planned. At first, this upset me, but I eventually came to understand that it is our responsibility to be prepared (and we cannot always control meeting outcomes). It is important to read the room and adapt meetings as needed. 3. Don’t overload yourself. During the early stages of my career, I was hesitant to decline additional work, even if my workload was already overwhelming. I was afraid of not meeting expectations. However, it is important to be aware of your own limitations and feel empowered to say “no” when necessary. While we may not always have a choice, it is important to carefully consider how much work you can realistically handle. Is it better to do a good job with what you already have on your plate, or lower the quality of your work by taking on more? Constantly being overburdened with work can prevent you from having the time and energy to identify opportunities for personal and team growth. 4. Don’t be a default meeting scheduler. There is a misconception that it is a PM’s job to schedule meetings, and as such I have often been asked to schedule meetings and take notes. However, this is not the primary focus of a PM role. To better manage my workload and prioritize, I have learned to say “no” to scheduling meetings unless I am driving the agenda or have a significant interest or stake in the meeting outcome. While I may make exceptions in certain cases (such as when I need to expedite something), I have learned to be more selective about the meetings that I agree to schedule. 5. Identify single points of failure (SPOF) for projects and their mitigations. As a Technical Program Manager in the tech industry, I have often managed projects where only one engineer is assigned to a project. This is a big risk, as that engineer is now a SPOF for the project. Whenever possible, it is advisable to request that at least two engineers share the workload of any deadline-sensitive, critical projects to reduce the risk of unanticipated personal emergencies or other risks. Apart from reducing the risk, this also helps with improving team morale as the engineers have someone else to bounce ideas off—and share the workload. 6. Put things in writing. It is important to document commitments or decisions made during your hallway or informal conversations in writing for future reference. Putting things in writing often leads to more careful consideration and follow-through from your team members. Personally, I have learned the hard way to always get things in writing to avoid any misunderstandings or miscommunications later. 7. Encourage proof-of-concept development. If your team is stuck in analysis paralysis, or if you are trying out a new technology, get management buy-in to spend time creating a proof of concept or a prototype. This can help to quickly demonstrate the potential of the technology or approach and facilitate faster decision making. 8. Include key stakeholders in reviewing status reports before they are published. Early in my PM career, I gave more importance to adhering to timelines than to aligning with key stakeholders. One time, I marked a project as red (behind plan) in a report without first discussing it with the manager of the team that was running behind. That manager was unavailable, and I did not want to delay publishing the status report. I went ahead and published the report without reviewing it with him. This had unexpected negative consequences, including the manager having to explain the red status to multiple members of the leadership team. Since then, I have been more careful about how I report project statuses. Before turning a project status red, it is important to consider possible mitigation plans and to review the status with all relevant cross-functional team members and their management. This may slow down the process, but it ensures that all key stakeholders are aware and aligned on the status. 9. Identify projects/programs to cancel. Deciding to cancel a project or program can be challenging, especially if a lot of time and resources have been invested. However, it is important to consider whether the project is still delivering the value that was expected. Don't let the sunk-cost fallacy (the tendency to continue investing in something simply because of the resources that have already been spent) influence your decision making. It's better to cancel a project and move on to higher-value projects rather than continuing to invest in something that is no longer worthwhile. 10. Be cautious about reporting program status as green/on track. In my experience, it is rare for all the projects in a program to be on track. If you do encounter a situation where all the projects seem to be progressing as per the plan, it’s important to carefully assess the situation and verify that thorough risk analysis has been done. While there are several other valuable lessons I've learned, I've distilled my most valuable lessons into these top 10 nuggets of wisdom. Project management veterans, what valuable insights have you gained throughout your career? Share your nuggets of wisdom in the comments section below! |