green team considers Agile db dev

[Juan Rolando Prieur-Reza]

Scott Ambler,
I have just scanned your book's table of contents and would like to ask you for an opinion on my problem. I have just been asked to plan the development of a new system that is database-centric. My problem is that the customer/management team is completely "green" (new) to defining and managing a software development project. They know nothing of J2EE, EJB-QL, and certainly nothing about development processes. They kind of know that "SQL" is a good database thingy. But they have the money and decision-making authority.
I, however, always work within a "process," such as UP. I need to corral these "leaders" into some kind of sw process. But they are not inclined toward any high ceremony workflows. I will have myself and one or two other experienced developers/DBAs at my disposal. So, my feeling is that I might give the "managers" a little reading material on Agile process.
Agile seems suited, but the managers/customers do not realize that they will have to participate in iteration (i.e. do work) to make the project happen. They are unprepared for seeing their nice "spec" change and change.
Question: Which chapters or additional material would you suggest that can both inform and persuade these not-yet-competent software managers to use Agile in this database-centric project?
Thank you in advance
[ January 14, 2004: Message edited by: john prieur ]

[Lasse Koskela]

You might employ the "project challenge factors" stats from the legendary Chaos Report by the Standish Group --> Changing requirements made #3 on the list and lack of user involvement is numero uno...

[Ilja Preuss]

Originally posted by john prieur:
Question: Which chapters or additional material would you suggest that can both inform and persuade these not-yet-competent software managers to use Agile in this database-centric project?

I doubt that any reading material will do the trick. What might be more effective is talking with them about their needs, showing them that you do understand their needs, and together try to find solutions you both can work with.

[Lasse Koskela]

Oh, the golden rule for persuading your management:
Make it look like it was they who came up with the idea

[Scott Ambler]

JP: I have just scanned your book's table of contents and would like to ask you for an opinion on my problem. I have just been asked to plan the development of a new system that is database-centric. My problem is that the customer/management team is completely "green" (new) to defining and managing a software development project. They know nothing of J2EE, EJB-QL, and certainly nothing about development processes. They kind of know that "SQL" is a good database thingy. But they have the money and decision-making authority.
Scott: They need to learn to trust your judgement on issues like this, otherwise why have they hired you? You should be able to explain your suggestion to go this way, discuss the trade-offs, and then they should hopefully support your decision. If things don't work like this I would take it as a warning sign and would reconsider participating in the project.
JP: I, however, always work within a "process," such as UP. I need to corral these "leaders" into some kind of sw process. But they are not inclined toward any high ceremony workflows.
Scott: Then cut down on the ceremony. RUP can be streamlined.
JP: I will have myself and one or two other experienced developers/DBAs at my disposal. So, my feeling is that I might give the "managers" a little reading material on Agile process.
Scott: Sure, can't hurt. Although a presentation focusing on benefits might be a better approach.
JP: Agile seems suited, but the managers/customers do not realize that they will have to participate in iteration (i.e. do work) to make the project happen. They are unprepared for seeing their nice "spec" change and change.
Scott: Focus less on the spec and more on the software. Also, if they do start to thrash point out the cost of doing so and try to steer them in a good direction.

Question: Which chapters or additional material would you suggest that can both inform and persuade these not-yet-competent software managers to use Agile in this database-centric project?

Scott: I'd stick with a presentation. Or, if that doesn't seem to work you might want to consider a short strategy session where everyone gets together and you talk it out. This is something I do a fair bit, see http://www.ronin-intl.com/services/rasp.html, if you're interested.
- Scott

[Ilja Preuss]

You might also want to look at "Introducing New Ideas into Organizations" for some tips...

[Juan Rolando Prieur-Reza]

Thanks, Scott and the others. Your feedback is quite valuable to me