3. Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. -- Wikipedia (http://en.wikipedia.org/wiki/Agile_software_development) What is Agile?
35. Agile does not require fewer written requirements but collaboration to identify themCase study: Vendor Cross Sales
36. Build a cross-functional product team Define and agree the product strategy Implement and promote feedback and collaboration tools Define “personas” and build for them Communicate, communicate, communicate 5 Tips for an agile implementation
37. Switch off instant messenger and email notifications Take one day a week to work outside the office Sleep at least 7 hours a day Go jogging in the morning Learn to say “NO” 5 Tips for productivity
38. Communicate, communicate, communicate Build a great product story and promote it like hell Make sure you respond to each feedback Don’t forget about the BUGs Fix them as they appear Define a “quick response” team Case studies about business value generated by ideas 5 Tips for a great collaboration
39. “Behind every great product there is a great product manager.” Marty Cagan – Silicon Valley Product Group Source: http://www.avangate.com/interviews/marty-cagan_15.htm One more thing…
41. Thank you! Daniel Nicolescu Chief Product Officer daniel.nicolescu@avangate.com
Hinweis der Redaktion
Hope everyone knows that picture. Allof us know what big difference can be between what customers ask and what they receive in the end. Not anymore! How? Using Agile as methodology/development framework.
There is a delicate balance between being agile and maintaining a certain level of focus. One of the great things about agile is that stakeholders can change their mind. Scrum (a flavor of agile) protects the team from too much change with the rule that scope cannot be changed in the middle of an iteration. This enables the development team to focus for at least 2-4 weeks at a time. However, the product manager needs to help enforce additional focus. Changing direction every 2-4 weeks will not result in the powerful and successful product releases of which you dream.
1. Recommended team members: 7-9
Internal discussion lists, announcements, pre-launch actions Start every meeting by reminding the BIG pictureHard work but you HAVE to do itSoftware? Then we will always have BUGs!