Format<\/strong> Stream<\/strong> Summary<\/strong> This talk shows how effective product ownership almost always requires a team with a variety of skills and backgrounds to be effective.<\/p>\n Product Ownership requires clarity of vision, alignment with organisational strategy, understanding of the development process and the ability to communicate with a wide variety of stakeholders across all levels both inside and outside the organization. The complexity of the role is most often more than a single person can (or should) cope with \u2013 effective product ownership requires a teamwork approach covering a variety of skills and knowledge.<\/p>\n This talk addresses the following key topics: Learning outcomes<\/strong> Mechanics<\/strong> 5 mins Introduction & scene setting Format<\/strong> Stream<\/strong> Summary<\/strong> Breaking up user stories can sometimes be as painful as a relationship break up – but it does not have to be like that!<\/p>\n Our experience has shown us that the key to getting full benefit from introducing Agile is in how the team’s work is broken up. When it gets difficult to see how to write small enough user stories, teams often resort to technical story cards. While this may give the team visibility of the work that is being done, the business is not seeing potentially implementable product, or early delivery of business value.<\/p>\n This talk will expose the real reasons for splitting up user stories and not just talk about doing it as a good practice – we must BE Agile not just DO Agile!<\/p>\n Using real-world examples, this talk will also offer a set of guidelines and some unconventional ways for breaking up larger chunks of work into valuable user stories that can help Agile teams become more successful.<\/p>\n Do you have a large User Story that you believe is impossible to split? Bring it to this session and be prepared to be surprised!<\/p>\n This interactive session will inspire and encourage every Agile practitioner to simplify User Stories and to think like a Customer.<\/p>\n Learning outcomes<\/strong> Mechanics<\/strong> Outline of the session<\/p>\n 0\u20133 May even challenge the audience to come up with large Users Stories that are unbreakable!<\/p>\n As the presentation title says, there will be 10 break-up techniques covered during the talk \u2013 3 of which will be done with audience participation. These will be treated as exercise for the audience. The mechanics of this will be is really simple regardless of the size of the audience.<\/p>\n In addition to that, there are several other opportunities for audience interactions throughout the presentation.<\/p>\n While this presentation is mainly targeted towards beginner and intermediate levels, expert Agile practitioners will also get a lot of benefits out of this talk. I also use this talk as a segment of the Agile Fundamentals and the Scrum Master Certification courses that I teach… it is ideal for going back to the basics.<\/p>\n I will be sharing a lot of tips and techniques for splitting up user stories that are unconventional and not commonly found in published patterns and methods. Audiences in my previous sessions connected really well with the real life user stories from real projects.<\/p>\n All attendees will also get to hear a lot of little ‘gems’ (general Agile tips and tricks of the trade) that are based on my hands-on experience in this area. The little ‘gems’ peppered throughout this talk ensures that participants of all experience levels are inspired!<\/div><\/div><\/div>
\nTalk\/Lecture<\/p>\n
\nThe Basics<\/p>\n
\nThe Product Owner is a crucial role in Scrum and many of the branded agile methods, however the way it is understood and most often implemented is wrong at best and very dangerous at worst.<\/p>\n
\n* The Product Owner Role
\n* Project Types
\n* The Product Ownership Team
\n– Product Ownership relationships
\n– Critical success factors for effective Product Ownership
\n– Product Ownership antipatterns & common mistakes
\n* Wrapup<\/p>\n
\nClarity in understanding of the difference between Product Owner and Product Ownership
\nUnderstanding of the variety of skills needed for effective product ownership
\nUnderstand what is needed for Product Ownership to be successful
\nUnderstanding the impact different product ecosystem elements have on the way teams are able to work
\nUnderstand the important relationships needed for effective product ownership
\nUnderstand some common mistakes and antipatterns<\/p>\n
\nThis is a talk with a number of interaction points where participants are asked to discuss points in small groups and share their thoughts with the remainder of the audience.
\nFor a 40 minute session the talk covers the following topics & rough timings: (based on feedback I have removed the group discussions and structured it as more of a tutorial)<\/p>\n
\n10 mins common patterns & antipatterns of product ownership
\n10 mins why product ownership really does need a team, what skills that team needs and the relationships that need to be built
\n10 mins critical success factors for product ownership success
\n5 mins wrapup<\/div><\/div><\/div><\/i><\/i><\/span>10 EASY WAYS TO BREAK UP...<\/span><\/a><\/h4><\/div>
\nIBM
\nDipesh Pala<\/p>\n
\nTalk\/Lecture<\/p>\n
\nThe Basics<\/p>\n
\nIn introducing Agile, a key element User Stories will allow a beginner to grasp core Agile values and associated principles, and use them as a primary vehicle for hearing the voice of the customer.<\/p>\n
\nThe presenter will be drawing upon their extensive Agile experience to share learning’s and use real case studies and examples of user stories to illustrate the following:<\/p>\n\n
\nThis talk is conducted in a fast paced, highly-interactive style to keep the audience engaged throughout. Light-hearted humour is used to make the analogy between relationship break ups and user story break ups.<\/p>\n
\nIntroduction and setting the scene \u2013 Why are break ups (be it real life relationships or User Stories) so difficult?
\n4-6
\nThe perfect User Story \u2013 is there such a thing?
\n7\u201332
\nBreaking up – a set of guidelines to follow when breaking up larger chunks of work (epics) into valuable user stories. The presenter will be drawing upon their extensive Agile experience to share learning\u2019s and use real-world examples of user stories to illustrate how this is done.
\nOne format that has worked really well for this presentation in the past is breaking up this (core) 25-min section of this talk into 3 segments (with 2 short ‘commercial breaks’ in between). During these 2 \u2018breaks\u2019, the session is turned into an open-forum kind of style where a couple of seed questions are planted to encourage some insightful discussions. A couple of example questions are When is the best time to break up? or Who should initiate a break up?. These sorts of questions get the audience really excited. These discussions are lead to become a nice segue into the next segment.
\n33-35
\nConclusion: Call to Action to convert every \u2018Excuse\u2019 into an \u2018Opportunity\u2019 to break up!
\n36-40
\nQ & A<\/p>\n