33001RE: [scrumdevelopment] Application Framework and database design
- Sep 30, 2008Well, my view is that, if you have some User Stories already, you can immediately get going on development (including stipulating appropriate 'relational' structures), and at the same time you can start planning future iterations and releases.
I am always interested especially in why people felt (and still find) it necessary and desirable to develop the database schema fully up-front. I woild also be interested in knowing why you have changed your position on this. As long ago as 1992 I published
an approach that I called Focal Entity Prototyping. Focal as in focusing on one entity (or relationship) and moving that through a development cycle of Entity Definition -> Table Definition -> Table Construction -> Data Form Construction (& reports and queries) and deliver that system component immediately. I have found this approach simple, effective and fast (and apparently rather puzzling to many practitioners and students alike).
It is interesting, from my experience in teaching at university level, that students are always so keen to rush ahead with defining the database schema on paper, and usually without the benefit of an entity modelling activity first. They seem so loath to do this vertical slicing and actually develop some working software. I find students to be great 'lab rats' who seem to find any and every way to defy good practice ... a bit like a slightly extreme example of development in industry :)
So ... grasp the nettle, as they say, and start delivering ... or insist on the outsourced developers to start delivering NOW!!
Date: Tue, 30 Sep 2008 17:30:02 +0000
Subject: [scrumdevelopment] Application Framework and database designI'm new to Scrum so please be patient.
Being an old waterfall guy, I'm accustomed to planning the application
framework (common objects, inheritance structure, error processing,
ect.) and designing the database up front.
To add to the complexity, we are outsourcing the development. I am
the Product Owner. The Scrum Master and the Team are outsourced and
do not have strong industry knowledge or a good understanding of our
day to day operations.
Our application incorporates 24 functional areas. It is my
understanding that each Sprint within the Scrum addresses a functional
area or a subset of the stories within a functional area.
It sounds to me like we are going to end up with a bunch of objects
pieced together and a database that is not all that relational. Or as
each new Sprint is implemented, we will need to rework other functions
and redesign the database.
I've got the User Stories for the first Sprint complete and the Team
wants to get started. Are we missing a step?
Thanks in advance for your help.
- << Previous post in topic Next post in topic >>