The Agile Methodology For Cross-Functional Teams


Published on

When it comes to deal with different interests that need to go in the same direction using an Agile style, definitely you are facing many challenges. Some of them are predictable but some others are not. Learn from real experiences and discover great tips for an effective Agile implementation, productivity and an functional communication across the team.

The presentation addresses the current challenges of product leaders and it unveils key development aspects great results – from learning to say “NO” to building a cross-functional product team, from building a great product story and promoting like hell to communicate, communicate, communicate, plus a study case with the challenges and the way we did it.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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!
  • The Agile Methodology For Cross-Functional Teams

    1. 1. Agile for Cross-Functional Teams<br />Daniel Nicolescu<br />Chief Product Officer at Avangate<br />
    2. 2. Software Development<br />
    3. 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.<br />-- Wikipedia (<br />What is Agile?<br />
    4. 4. <ul><li>Delegate and trust people
    5. 5. Acknowledge change as a standard
    6. 6. Promote constant feedback
    7. 7. Work in short iterations
    8. 8. Focus on business priorities
    9. 9. Inspect and adapt</li></ul>Agile principles<br />
    10. 10. <ul><li>Deliver high business value in short time
    11. 11. High level of customer satisfaction
    12. 12. Working software is delivered all the time
    13. 13. Quick implementation time for feedback
    14. 14. Excellence by innovation</li></ul>Agile benefits<br />
    15. 15. <ul><li>Requires very experienced people to understand both business and technical
    16. 16. Hard to provide an accurate time and cost estimate at the beginning of the development cycle
    17. 17. Hard to maintain FOCUS</li></ul>Agile disadvantages<br />
    18. 18. Market expectations<br /><ul><li>Enable Avangate clients (software vendors) to cross sell products from other clients.
    19. 19. High conversion rates
    20. 20. Make it profitable</li></ul>Case study: Vendor Cross Sales<br />
    21. 21. Challenges<br /><ul><li>One feature, many ideas
    22. 22. Make it an “easy sale”
    23. 23. Deal with different interests within the same team
    24. 24. Make it work</li></ul>Case study: Vendor Cross Sales<br />
    25. 25. How we did it<br /><ul><li>Separate meetings with each department
    26. 26. Business requirements for company leaders
    27. 27. Product specifications (mockups, usability)
    28. 28. Feedback meetings on development stages
    29. 29. Final version presentation in front of the company
    30. 30. Official launch – a great success?
    31. 31. Clients feedback – final touch!</li></ul>Case study: Vendor Cross Sales<br />
    32. 32. Lessons learned<br /><ul><li>Validate each decision with the team – always!
    33. 33. Get feedback
    34. 34. Write down requirements and constantly update them
    35. 35. Agile does not require fewer written requirements but collaboration to identify them</li></ul>Case study: Vendor Cross Sales<br />
    36. 36. Build a cross-functional product team<br />Define and agree the product strategy<br />Implement and promote feedback and collaboration tools<br />Define “personas” and build for them<br />Communicate, communicate, communicate<br />5 Tips for an agile implementation<br />
    37. 37. Switch off instant messenger and email notifications<br />Take one day a week to work outside the office<br />Sleep at least 7 hours a day<br />Go jogging in the morning<br />Learn to say “NO”<br />5 Tips for productivity<br />
    38. 38. Communicate, communicate, communicate<br />Build a great product story and promote it like hell<br />Make sure you respond to each feedback<br />Don’t forget about the BUGs<br />Fix them as they appear<br />Define a “quick response” team<br />Case studies about business value generated by ideas<br />5 Tips for a great collaboration<br />
    39. 39. “Behind every great product there is <br />a great product manager.”<br />Marty Cagan – Silicon Valley Product Group<br />Source:<br />One more thing…<br />
    40. 40. ?!?<br />Questions<br />
    41. 41. Thank you!<br />Daniel Nicolescu<br />Chief Product Officer<br /><br />