I've heard from product manager that I have worked with in the past these jargons when it comes to breaking down project. What does that mean? Does it apply to product mgmt or software development too?
Priority?
Priority. P0 - essential product feature. P1 - important, but the product can work without these. P2 - nice to have
Never heard of it. And I’ve been doing it 15 years.
Priority. P0 is top priority. Software development could adopt it like launching with just P0 requirements.
Mostly P = priority
P0 - Don’t release without. Priority over all. P1 - If we are running out of time, scrap these and call it in upcoming sprints. P2 - Can wait until all others are done, usually nice to haves. I don’t usually see P2s.
Thanks!
Phase 0 and Phase 1?