PPP: Progress, plans, problems Report

What is PPP weekly reporting?

  • The most efficient and widely used status reporting framework
  • Stands for Plans, Progress, and Problems.
  • Used in organizations in situations like an employee to manager, team member to team or CEO to board, investors, and advisors reporting.

Companies using PPP 

  • Skype
  • eBay
  • Facebook
  • Apple 

PPP Report Structure

Each report consists of three sections:
  1. Progress: Employee's accomplishments, finished items, and closed tasks for the period ending.
  2. Plans: Goals and objectives for the next reporting period.
  3. Problems: Items that are stuck and can't be finished. Problems often need help from someone else, not just the employee.

Plans

  • People should list the 3-5 most important things they want to get done this week.
  • Not a list of every small task you are doing this week.
  • Use it as a priority list of the most important things you want to focus on. 

Progress (What is Done)

  • It is what you have completed during the week.
  • If you worked on something that wasn’t planned but is important enough to share, you can add it straight to the Progress section.

Problems

  • Two ways to use the Problems category.
  • The first way is to move a task from Plans to Problems when there are obstacles to execution. The task will stay under problems until it gets resolved.
  • The second way is to use Problems to list all of the other issues or challenges that you faced during the week if you feel like they are important enough to share with others.

Benefits

  • OKRs set goals. Weekly plans remind you to achieve them. 
  • Planning helps to manage time and prioritize.
  • Planning and progress sharing is not something people do for their manager, it’s something they do for the team. Team members need to see what others are working on to offer timely feedback and keep up with the updates.
  • When seeing each other’s plans, team members can offer help when it’s needed, have a better overview of what’s happening, and learn more from each other’s experiences.
  • When your team members are keeping their PPP forms updated, this saves everybody time and energy. There’s no need to spend extra time in meetings to share what has been done.

Comments

Post a Comment

Popular posts from this blog

Software Architecture Techniques - Part 6

Question 1: What is the 20-minute rule, and when is it best to apply it? Answer: The "20-minute rule" for software architects is a time management technique that encourages dedicating short, focused bursts of time (around 20 minutes) regularly to learn new technologies, tools, or industry trends. The goal is to increase the architect's technology width, which refers to broadening their knowledge and understanding of different technologies and practices beyond their current expertise. Here's how the 20-minute rule can be applied: Consistent Learning : Set aside at least 20 minutes each day or several times a week to engage in learning activities. This could include reading articles, watching videos, attending webinars, or exploring documentation related to new technologies or architectural concepts. Focused Approach : Use the 20-minute sessions to maintain focus and avoid distractions. Eliminate interruptions during this time and fully immerse yourself in the learning ...
Read more

Software Architecture Techniques - Part 2

Question 1: What are the two dimensions of the risk assessment matrix? Answer: The risk assessment matrix typically consists of two dimensions: Likelihood : This dimension assesses the probability or likelihood that a risk event will occur. It is often represented on a scale from low to high or with numerical values (e.g., 1 to 5, where 1 is low likelihood and 5 is high likelihood). The likelihood helps in understanding the chances of the risk event happening. Impact : This dimension evaluates the potential consequences or impact of the risk event if it occurs. It is also represented on a scale from low to high or with numerical values (e.g., 1 to 5, where 1 is low impact and 5 is high impact). The impact helps in understanding the severity of the risk if it materializes. By combining the likelihood and impact assessments, organizations can categorize risks into different levels of criticality, such as low, medium, and high risk. This information is valuable in prioritizing risk respon...
Read more

Software Architecture Techniques - Part 3

Question 1: What is irrational artifact attachment, and why is it significant with respect to documenting and diagramming architecture? Answer:  Irrational artifact attachment is a cognitive bias that occurs when individuals become overly attached to certain artifacts, such as documentation and diagrams, without considering their actual usefulness or relevance to the architecture or project. It refers to the tendency to treat artifacts as inherently valuable or important, even when they may not provide substantial benefits or are outdated. This bias can be significant with respect to documenting and diagramming architecture for several reasons: Misleading Focus : When individuals are irrationally attached to specific artifacts, they may focus on maintaining and updating those artifacts rather than on the actual architectural decisions and their impact on the project. This can lead to a misallocation of time and effort. Loss of Agility : Outdated or unnecessary artifacts can impede ...
Read more