11/11/2022
Got a chance to listen to Sawko, Founder at Startup Grind here in Liverpool. It is amazing how startups can connect with each other when it comes to the journey of a product from bootstrapping till scale. I got a chance to learn a lot from this event by connecting with passionate founders trying to disrupt existing business models.
It was really nice meeting Moises Barbera Ramos John Beesley James Bedford Helen Cross Daniel Billington. Hope to see you all again.🌞
I want to thank Jonny Clark for making this event happen. More power to you 🏆
03/11/2022
Guys, I will be giving a session on business plan. Feel free to join using the below link;
https://pitb.zoom.us/j/96470391103
Ibrahim Lughmani | Ex-IBMer, would be joining us at to share his expertise in designing a perfect business plan for beginners
Ibrahim saw a huge market gap & realized that big platforms are taking over the market share of local businesses & wanted to stand for the local economy by creating a digital platform that connects local buyers & sellers with a lean business model through a supercharged marketplace.
Session Date: Friday 4-Nov-2022
Timing: 10:00 AM
Venue: NEP NICs Center, University of Gujrat
Punjab Information Technology Board (PITB)
Ministry Of IT & Telecom
18/10/2022
Q: What is product strategy & how do you calculate its success?
Product Strategy is identifying gaps, leveraging whatever is available to execute a product plan in a tactical way that could make it successful. To calculate impact, create KPI's based on those strategic initiatives.
13/10/2022
We discussed about the RICE framework in my previous article. How about we talk about other feature prioritization methods today.
There are several methods that can help product managers with feature prioritization depending on the stage of a product. But how do you get list of features in the first place? I would suggest using research, empathize, define & ideate from Design Thinking principles. You could also do competition analysis to get things started.
KANO Method:
This method is ideal at launch stage & uses user feedbacks to identify what they would like & expect in a product. By doing this exercise, product managers would come across features that users either don't care about or dislike. A specific approach is recommended while conducting such research i.e. maintaining user diversity, reasonable sample size and how to ask questions related to how users feel about a feature. Rather than leaving the answers to these questions open-ended, you want to have respondents use a 5 point scale. i.e. Like it, Expect it, Don’t care, Live with or Dislike it. This makes analyzing the data easier and helps in building user personas. Once you have scored the features, you can simply prioritize them based on their scores.
MoSCoW Method:
Used usually at the MVP stage or for internal projects, this method focuses on the features that adds maximum value, save cost and time to deliver a product through stakeholder feedbacks. Product managers can then score individual features and make decisions based on available resources and time. MoSCoW is an acronym made up of the first letters. The two O's have been added to make the word 'moscow' readable, they don't have any meaning themselves. The M stands for 'Must haves', S for 'Should haves', C for 'Could haves' and W for 'Won't haves' or 'Would haves'.
Opportunity Scoring:
Also called gap analysis, focuses on the features that the user considers important but is underdeveloped or disappointing. This can bring innovation if product managers focus on what the users are trying to achieve through their feedbacks. To calculate opportunity, we need estimated score for importance of a feature and satisfaction level of the user. The equation to find out opportunity score is
Opportunity = Importance + Max(Importance - Satisfaction, 0).
I will talk about what method to use when and why in my next article.
10/10/2022
Welcome back guys! I hope you all had a great weekend. 🤩
In my previous poll, I asked about what prioritization method do you guys most commonly use & the majority poll suggests MoSCoW. No doubt its a good method. How about I ask you guys another question?
Why MoSCoW? Why not KANO or any other method? How do you decide which method to choose for task prioritization? 🤔
I will let you guys answer & then share my article on how to choose the right method. 🤠✌
05/10/2022
After my previous post about task prioritization, people are asking for more clarity on the subject. Here it goes. 👇
We all know that product management in agile is all about maximizing outcomes with what is available as resources. Once you have done the right research, built user personas & identified user needs, you would have a list of features waiting to be developed. Considering that ex*****on is everything when it comes to making products successful, how would you prioritize what to develop first? Would you choose a feature that you are excited about? or would you choose a feature that one of the stakeholders is making fuss about? How would you decide on what to deliver first?🤔
A product has different stages. A startup focusing on an MVP would have different goals while a fully developed product might focus on scale. This makes the prioritization of features dependent on the goals of the organization which may change from time to time based on the speed of development, stage of product, market situation or product vision. When product managers have clear goals, only then can they prioritize tasks to generate maximum outcomes.
Now that you are clear on goals & know what to achieve, you can prioritize tasks based on cost vs impact analysis and to help you with that, there are some methods that you could use like RICE, KANO, MoSCoW and many more. Remember that these are just methods that could help you with task prioritization and would not always lead towards the right decision because sometimes impacts cant be calculated precisely. We will talk about the risks involved in detail when we discuss each method separately.🤩
Did you find this article useful? How do you prioritize your tasks? You can make this article more impactful by sharing your experience in the comments or by sharing this article with your professional network.
05/10/2022
After my previous post, people are asking for more clarity on task prioritization. Here you go guys 👇
Feature Prioritization - Overview
After my previous post about task prioritization, people are asking for more clarity on the subject. Here it goes.
04/10/2022
People ask me how I manage unplanned tasks. Here it is. 👇
Keeping organization goals in mind, i calculate the impact vs cost of the task. I can score it using appropriate scoring model (RICE maybe) and compare the score with the planned tasks for the sprint. I will also see if the task is not too big & if dev team has a cushion to squeeze the task in the sprint. If not, but the impact is high as compared to the planned tasks and is affecting goals and targets, I would swap it with a task that scores less and has the same or less effort estimates. If the impact isn't so high, doesn't affect goals and there is no cushion in the sprints, I will plan it for next sprint. 🤠
30/09/2022
I have spoken about the importance of not just research but the right research and this famous quote concludes it.
13/10/2022
10/10/2022
07/10/2022
05/10/2022
05/10/2022
04/10/2022
30/09/2022