Agile2013 It's All About the Context
elizabethwoodward 270001YW5Q Visits (2128)
One of the things that I enjoy most about conferences like Agile2013 is the opportunity to hear different perspectives. It reinforces that a practice that one team deems critical may be utterly unhelpful to another team working in a different context.
Two people were discussing why there might be so much demand for a session on negotiation:
Both were viewing the session, the practices, and the potential challenges from the context of their own development environments and came to completely different conclusions. Each conclusion made sense based on the context.
The first person was on a 5-person continuous delivery team developing one capability for an application related to one stakeholder. The other came from an environment where he developed packaged software for many customers in different industries with different roles (end users, business owners, IT administration, etc.)
Just as we learned in creating The Practical Guide to Distributed Scrum as a community, we each bring a unique perspective. We have so much to learn from one another by sharing practices and techniques that have worked for us, sharing things that have not worked and digging into the reasons for discrepancies in experiences.
Application development, embedded/systems development and packaged product development bring very different experiences. Enterprise complexity, geographical distribution, domain complexity, team size, capabilities, personalities and many other factors have a significant influence.
I'm looking forward to learning more this week from other attendees, as well as presenters, at Agile2013!