Ciklum Seminar Zurich June 25, 2013 Dmitry Kanevksy (Ciklum)
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Ciklum Seminar Zurich June 25, 2013 Dmitry Kanevksy (Ciklum)

on

  • 325 views

Why is the „Product Owner” role so important in agile development and particularly in nearshore team settings? What can and will go wrong, if roles, methods, and tools for proper requirements ...

Why is the „Product Owner” role so important in agile development and particularly in nearshore team settings? What can and will go wrong, if roles, methods, and tools for proper requirements gathering, documentation and prioritization are missing? This session gives a brief overview of how an ideal setup looks like: Integrate your software development teams into the requirements development process, share business knowledge and responsibility for product delivery!

Statistics

Views

Total Views
325
Views on SlideShare
325
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Ciklum Seminar Zurich June 25, 2013 Dmitry Kanevksy (Ciklum) Presentation Transcript

  • 1. Agile Product Management Strategic considerations and successful patterns for nearshore software development Dima Kanevsky, Consulting Lead
  • 2. We are going to talk about • Strategic considerations of Agile Product development • Product Owners role and key fallacies in a nearshore setup • Four unsuccessful and five successful patterns in Agile Product Development which let product managers succeed with nearshore teams
  • 3. NOT going too deep into the ‘right’ practices
  • 4. We are too much overcomplicating software development
  • 5. individuals Organizations Complex ecosystems
  • 6. Risk Return Problem is unknown and solution is unknown Problem is known, solution is known Problem – solution fit Solution is known, problem is not known
  • 7. Effective Efficient Product success
  • 8. Manager’s wet dreams
  • 9. ‘…aim at commanding positions within a given market segment’ - Davidow, Marketing High Technology Monopoly or..
  • 10. Lean principles to the rescue • Mitigate risk • Minimize inventory • Eliminate waste
  • 11. ‘…68% of the features are used either once or never’, Gartner, 2008
  • 12. How to produce value?
  • 13. The number one the most critical for software success and return-on-investment is effective user adoption - Sand Hill Group and Neochange, 2011
  • 14. Three biggest challenges of a product owner in a nearshore setup • creating a sense of ownership within the team • sharing business context to engage the team in decision making • inefficient and costly communication
  • 15. What can and will go wrong
  • 16. #1 PO is a bad representation of a user
  • 17. # 2 too much focus on a product vision
  • 18. ‘Coming up with 15 or 20 product features proves to be easy. It's figuring out which 3 or 4 would cause someone to buy the product that is difficult’, - Hillsmith.
  • 19. # 3 too much design documentation
  • 20. Right approach
  • 21. # 4 too much communication
  • 22. The less people talk the better
  • 23. How an ideal setup looks like
  • 24. #1 collaborative requirements gathering and validation
  • 25. #2 inject business context holder in the team
  • 26. #3 Opt out for a fully distributed scrum
  • 27. #4 Bring the team together
  • 28. #5 Treat people as adults