Format: This will be presented as a talk with data from several case studies. The talk will be followed by discussion and Q&A
Duration: 60 minutes
Abstract
Have you ever left work after 10 or more grueling hours and felt that you had accomplished nothing? If so, this talk is for you. In this talk we will use several case studies to explain a working method we simply call "getting things done". This session will draw on case studies to explain a method that enables teams that work in software companies, but not on software project to rip the benefits we so commonly associate with Agile/Scrum in the software development industry but without mentioning the words Agile or Scrum. Using this method, the teams involved have not only increased their productivity but, most importantly they feel better at work and in control of their time.
Description
The presenter will walk through several case studies explaining the constraints that led him to test an Agile-inspired method outside the software development group at a medium sized company. During the session there will space for questions to enable the
participants to understand in detail some of the principles behind the method to be presented.
Draft agenda
10 min - introduction and explaining the problematic
40 min - case study walk through + Q&A
10 min - final Q&A and wrap-up
Biography
Pekka Usva is an experience product manager who has a background in software development. Having worked in many roles in a software company, Pekka understands deeply the complex environment in which software development is done today. From the technical challenges to the sales and marketing aspects.
Pekka has completed an MBA in product management and has for the past years been developing his team to be a world-class product marketing team.
Comments (3)
Jul 23, 2009
Lasse Koskela says:
This sounds like an interesting cross-discipline application of agile methods, a...This sounds like an interesting cross-discipline application of agile methods, although I have trouble understanding the abstract where it talks about software - could you clarify that section a bit?
Jul 30, 2009
Vasco Duarte says:
The mention of "software" in the abstract is just to contextualize the work. It ...The mention of "software" in the abstract is just to contextualize the work. It was done in a software company, but not by software development people. Rather it was in Product Management and Sales.
Aug 05, 2009
Pekka Usva says:
Back to Lasse continuing what Vasco already started... If you are looking this f...Back to Lasse continuing what Vasco already started... If you are looking this from company's functional structure point of view we applied the working method to projects where staff represents people from product and solution management, product marketing and channel management. Projects respectively represent cases like "launching a new product and pricing model to channel", "preparing roadshow activities and content for major product launch".