“Do readers think that the management should be part of the data modelling process to demonstrate the significant value of a solid data architecture?”
In agile methodology, the customer is involved in user stories, setting priorities and clarifying any requirements. And in the parallel, data modelling carries on and is refines in every sprint. If the customers are collocated it increases the accessibility, it is easier to communicate as face-to-face communication is more helpful than emails. The quality of user stories and data model depends upon how much the customer understands the business operations. According to (Koch, 2005), the Agile Manifesto’s value “We have come to value customer collaboration over contract negotiation.”
Customer responsibilities in agile methodology include (Koch, 2005; Highsmith, 2010):
- Establishing requirements/user stories
- Project/Increment planning by setting priorities on requirements, selecting them for every iteration
- Reviewing the outcome of every sprint
- To give feedback and see if any element needs changing
- Evaluating and prioritizing requirement changes
- Confirming if the deliverable of every sprint meets customer needs
- Customer is solely responsible for any change in the project scope
One of the many advantages following agile methodology is instant feedback from the customer and his involvement.
References:
Highsmith, J. (2010) Agile Project management. 2nd edition. Boston: Pearson Education Inc
Koch, A.S. (2005) Agile Software Development: Evaluating the Methods for your Organization. Norwood: Artech House, Inc.
