Listen to this podcast by Adam Bader on “This is Product Management” with Anuraag Verma. For me, this is one of the best among the others in the series so far. I like the way how Adam relates Product Managers as Problem Managers and how he talks about the importance of psychology in solving real problems over the perceived ones and to what extent you should be using that privilege. I like his empathy towards users.
If you don’t have time, listen to the last 10 min of the audio at least starting at 29:00s. He talks about why so many products fail and physiologically how big companies are hacking and exploiting (to the roof) natural human behavior to their own advantage.
I am glad, Adam Bader brought this is up in the end. Technology needs to focus on real-world problems such as Transportation, Sustainable development, Climate Change, Healthcare, Poverty, etc. Too much focus on smartphones, connecting people digitally, building apps that do not solve problems must stop. He talks about Space Tourism. Personally, I do not think, space tourism is the world’s current problem. It is more of a want for riches than a need.
Podcast Link is here: http://tun.in/tlcege
In an Agile software development environment, a part of the Scrum framework, Sprint is a time-boxed event for the scrum team to deliver a small product increment which is typically a releasable product. Usually, Sprints are one to four weeks long. Every sprint, the scrum team picks up a number of product backlog items and make a commitment to move them to a done state as per the definition of done. The size of each product back item is generally expressed in terms of story points. They are like units of user stories that can be addressed in a sprint. A number of story points completed at the end of each sprint provide a very good understanding of the team’s capacity or WIP (work-in-progress) limit. Depending on the complexity of sprint backlog items and level of productivity, the team can complete a varied number of story points at the end of each Sprint. In order to estimate the average velocity of the Sprint, the Product Owner simply uses the arithmetic average formula. See the below example.
Let’s say we have completed several sprints and we have a record of the number of story points completed in each sprint.
Sprint Backlog Items = 5
Total Story Points Targeted = 22
Total Story Points Completed = Sprint 1 Velocity = 18
Sprint Backlog Items = 6
Total Story Points Targeted = 24
Total Story Points Completed = Sprint 2 Velocity = 20
Sprint Backlog Items = 7
Total Story Points Targeted = 32
Total Story Points Completed = Sprint 3 Velocity = 24
Sprint Backlog Items = 6
Total Story Points Targeted = 26
Total Story Points Completed = Sprint 4 Velocity = 26
Average Sprint Velocity
Total Sprints = 4
Average Sprint 4 Velocity = (Sprint 1 Velocity + Sprint 2 Velocity + Sprint 3 Velocity + Sprint 4 Velocity) / Total Sprints
Average Sprint 4 Velocity = (18+20+24+26)/4
Average Sprint 4 Velocity = 22 Story Points