So you've started the project and identified your customer and her objectives, and identified the roles: the distinct kinds of users who will be interacting with the website application. You've installed Drupal and begun getting your prototype on the road by creating your first cut of business objects based on a lexical analysis of the user story titles. You are almost at the point where you can ask the client for feedback to make sure the roles and list of user stories look complete, and to write the user stories. Coherency will be enhanced by her using the semantics offered by the list of business objects and the limited functionality you have started to put together based on input received so far.
Figure 3-1 shows the elaboration iteration as it looks now.
It doesn't look like it, but you have actually done quite a lot of work already. Still, there's plenty left to do. Let's see how much we get done in this sprint, starting with the third task: get initial feedback from the client Pam (who actually does live in Alaska!) on Skype, and show her the website deployed to the test site (see Chapter 2).
Before that, though, let's just review how the first task, creating an initial environment, is implemented and how you can synch up your development box and your test site on a daily basis so that the client can always check out the latest relatively stable version on the test site.
To build upon a solid foundation, it is necessary ...