![]() ![]() The “sweet spot” of Scrum, born in the center of a Venn of building the right thing, building the thing right, and building it fast. The aim of these new frameworks was to create an agile way of working – let’s pinch zoom in on Scrum. In the 90s some cool cats got together and created new and exciting frameworks like Scrum, XP, Crystal, and DSDM. So they would start the process again, and often again – there had to be another way. Often, what came out at the end looked nothing like what these poor product managers had in mind. Product managers would spend ages hammering out details, documenting it to within an inch of its life, then throw it over the wall to development. A potted history of product ownersīefore product owners and agile, there were product managers and waterfall, and they were slow. In this article, we will build upon the original product owner description and drill down into what it means to be a product owner, where they sit, and what the specific responsibilities are.īut first – a history lesson. ![]() We’ve written about the difference between a product manager and a product owner before, you can read about that here. Defining product owner responsibilities should be a pretty easy thing to do right? Right? Well… sort of, not really, and here’s why – the definition of product owner ranges from company to company and, to make it even more convoluted, a product owner and a product manager are often confused – their roles and responsibilities are blurry at best and overlapping at worst.Īlso, does the title really shed light on what the job is? Does a product owner actually ‘own’ the product? No, they don’t – they own building the right product – but… I’m getting ahead of myself we’ll come back to that later. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |