Wicsa7:Tutorials:TAGL
From WICSA Conference Wiki
TAGL: Architecture and Agile Methodologies—How to Get Along
Issues raised during the discussion
- Distributed teams
- Characteristic of agile planning
- Perception of agile as something new, different
- Outsourced teams
- Assuring appropriate decomposition across enterprise systems
- Getting customer to commit resources
- How can product that need regulatory approvals for safety use agile?
- How to deal with those in the organization that see agile as an excuse to be “cowboys”?
- How does responding to change is the agile sense really different from good scope management in a non agile project?
- Once you remove religious adherence to specific practices, are the “principals” or agile that different from other forms of iterative development?
- Dealing with virtual teams
- I see to much rework
- Is Agile just new practices or are they truly new principles?
- Getting customer to work in a different way (i.e. more collaboration)
- When do developers propose “refactoring” into the work as it might not give the customers any short term benefit for their organization
- If the customer is key, how can we be confident of the customer’s skill at understand and learn to help converge on what is needed?
- Architect + agile + offshore development: is this a XXX for success?
- Getting responsive customer feedback on every “heart beat”.
- Different teams in the organization is working with different development models, i.e. agile, waterfall, than does an architect work in this environment?
