Will the Real Slim Shady please stand up?
Guess there's a Slim Shady in all of us…but the real slim shady - Product Owner role - today is mostly ignored and misunderstood across most organizations. This talk highlights the confusion and the need for recognizing the product owner role as a ‘first-class’ citizen across the industry.
The session will help you take a closer look at your current product owner team, and compare with an ideal product owner role, and in the end suggest possible ways to align your product organization better. If you are already a product owner or managing a team of product owners, you need to join this conversation and pick and/or suggest some of your own remedies.
Outline/structure of the Session
- Current dynamics of a product owner role [5 minutes]
- Future directions for the product owner role [5 minutes]
- Describe the skill gaps observed in the product owner roles and possible remedies for improving the situation [10 minutes]
- Summary and Call for Action to the Target audience [5 minutes]
Refer the accompanying slide share and the video below for an earlier rant, which talks about the ‘Product Manager Version 2.0’ aka. the “real slim shady” describing the ideal Product owner role, who is empowered and can take decisions, while communicating internally both with the teams and externally with customers and sponsors. Additional blog posts highlight the existing gaps, and the low trust relationship between the product owner and the technology team.
- Introduction to Product owner role (basic since this is an intermediate level talk)
- Who are the product owners today and who they really should be
- What are the critical skills that product owners require to succeed in this role
- Key Takeaways and Next Steps for Action in your organization !
As a session attendee, you will realize that the 'right' Product Owners are critical to be a "truly successful" Agile team; and hence be able to review the "current" product owner job descriptions in your organization versus the "ideal" skills expected. These learnings will immediately provide the team\yourself insights into understanding your existing product owners capabilities better, be able to identify the gaps, and align the team\yourself to leverage the strengths better and work on the improvement areas, in the end delivering superior business value as a combined force.
At a broader strategic level, you can immediately start to educate your hiring teams about the need for a well defined career path, training needs and recognition of the product owner role.
Hiring Managers, Agile Change Agents, Product Owner, Product Managers
schedule Submitted 2 years ago
People who liked this proposal, also liked:
Speed 2 Value.. helping large Enterprise IT to be in the game..
Technology has blurred the lines between the digital and traditional methods of dealing with a consumer of any Global Enterprises. The Business Process and IT is no more separate, in most of the industry verticals the Business is driven by IT. Constant Innovation around IT has become the new normal to the Enterprises to meet rapidly changing consumer expectations and behavior dynamics.
More connected consumers, automated processes, and sophisticated analytics place unprecedented demands on IT functions. Many Enterprises are struggling to cope, and they seek to deliver on new demands by adding piecemeal elements to their existing operations. This is easier said than done. Reinventing the IT function at Global Enterprise requires far-reaching changes, from talent to infrastructure, tools, delivery models, partnership model.
This experience report brings strategy of 2 speed IT, through which Infosys helped its Global top 10 clients to 'renew' its IT related to Digital & Mobility space using Agile as a key lever.
This session gives you experiences, practical on the ground challenges, stakeholder and vendor complexity and approach and journey towards Speed 2 value. Also I am pairing with Alok Uniyal who is senior leader at Infosys and a CIO coach who helped 50 plus clients to transform their IT organization in last 20 years.
Distributed Agile PatternsShriKant Vashishtha
schedule 2 years agoSold Out!
Way back in 2008, when I started working in Agile, there was enough material available on Scrum and. However when it came to distributed aspect of it, people were still struggling with it. Based on working for years in this fashion, I realised that communication, trust, transparency and innovation are the core fundamental values towards successful distributed Agile implementation.
In other words, as most of the problems were caused by softer aspects of skills (misunderstanding, miscommunication, non-availability of people, mistrust etc), humanizing the distributed team experience looked like the key for successful distributed Agile implementation.
Based on working with distributed teams over the years, we discovered some distributed Agile patterns. Some of them got blogged from time to time. Those already available in form of blogs are as follows:
- Distributed Pair Programming
- Local Retrospective
- Agile way of documentation
- One Team Multiple Projects
- The nut/bolt pattern for distributed Scrum development
- Chain-Link Pattern
- Virtual One Room
The session is to share the these patterns and more (when to go for distributed Agile and when not etc)
Tales of (not so) successful Dev-Ops
Welcome to the crazy world of Dev-Ops, where the tales span the spectrum from gruesome, grizzly to the heavenly and flowery bliss!
The silo’d structures, the agonizing buy v/s build debates, the departmental handoffs, tooling and of course the cultural barriers, which all add fuel to the story unfolding in our brave new dev-ops world. But sometimes there are silver linings and the heavens part way for the shining stars to reveal their true glory.
Join our session to listen to the tales of our (not so) successful dev-ops, and learn the lessons from our experiences.
Are we becoming profitable with agile?Saket Bansal
schedule 2 years agoSold Out!
Why organizations are adapting towards agile? Is it to get most out of their resources or is it about doing the right thing?
Traditional mind set of achieving high productivity and using resources efficiently does not change easily, even when organization moves to agile they remain more and more worried about the team velocity. When I meet agile practicing companies or I attend event on agile I find that most of
the focus is on delivering product backlog efficiently. We see lot of talks on how to make team more self-organizing so that they can do the things faster. Even after moving to scrum or agile we keep ignoring the warning
“There is nothing so useless as doing efficiently that which should not be
done at all.” —Peter F. Drucker
When most of the organization starts with agile they takes it as an engineering process, and most of the team focuses too much on velocity, while to get maximum out of agile we need to look at Enterprise Agility, we need to look at an organization’s entire value stream—from idea to implementation, from concept to consumption.
My talk would be focusing on need of organization agility and will introduce one of the monitoring tool “Life Cycle Profitability “which can help organizations in getting answers of questions like :
- Should we delay the release by one month to fix the defects ?
- Should we reduce the cycle time by adding one more team?
- Should we delay the release to add functionality?
- Should we delay the project by one month to get more innovative ?
Life Cycle Profitability is based on principle “Take an economic view” introduced in book:The Principles of Product Development Flow , Donald G. Reinertsen . In my talk I will be showing how we can convert proxy variables like cycle time , velocity , technical debts into Life Cycle Profit.
I presented part of this concept in one of the conference and got good response, but I will create fresh presentation for this talk, since this time I will put more focus on expanding the model to calculate the Life Cycle Profit.
Self Organizing: How to Lean-in to difficult conversations?Asheesh Mehdiratta
schedule 2 years agoSold Out!
Leaders today are looking at “self organizing” agile teams to WIN ALL the battles on Auto-Pilot. Nice try is all I can say !!
...though some teams surely do succeed (lucky guys?). But most teams are not so lucky, and get constrained by the organizational systems, processes, boundaries, and need an outside-in perspective or a divine eye to kick start their next improvement journey. Sometimes a leader takes on this divine role to guide them on this journey.
This talk aims to provide the leaders a toolbox for using Lean conversations, to spark their next team improvement journey, by designing improvement kata’s, while slowly inching the team forward towards nirvana !! Divine Bliss !! .... So if you are a leader looking at learning and implementing the simple techniques of guiding the team on a self improvement cycle, leading to true self organizing team, join us.
Enabling Emergent TechnologiesFred George
schedule 2 years agoSold Out!
The latest new, cool tool comes along. Will you be allowed to use it? Probably not! So how can you change that?
This presentation looks at the introduction of new technologies at three companies, The Forward Internet Group in London (a startup originally, now grown to 400+); MailOnline, the online version of the Daily Mail newspaper from London (a very old organization with an existing IT shop); and Outpace, a Silicon Valley startup.
In both cases, Programmer Anarchy was introduced. This managerless process (not unlike GitHub in its value propositions) empowered the programmers to make technology choices and to freely experiment with new technology. In the case of Forward, massive growth and profits ensued. In the case of MailOnline, redevelopment of core systems into new technology has been launched, and expectations significantly exceeded.
This presentation will touch on the various aspects of implementing Programmer Anarchy at MailOnline:
Team building through programmer training
Pilot project without managers, BA’s or dedicated testers
Reinforce the model with new HR structure emphasizing skills over titles
Create selforganizing teams of 58 developers (multiple such teams)
Charter teams with a specific project, and let them deliver
- Avoid artificial schedule pressure
The intent is to provide a possible roadmap to get your latest technical toys moved into production systems.