book chapter: Methodological Considerations

[Pradeep bhatt]

Chapter "Methodological Considerations" - What is about ?
Thanks,Pradip
[ January 18, 2006: Message edited by: Ilja Preuss ]

[Cliff Berg]

Pradip, the chapter "Methodological Considerations" is to me the most interesting chapter. That is because software is built incorrectly when the process is broken. Fix the process, and the software will get fixed. This chapter examines what is needed in a methodology - any methodology - in order to be able to develop high-assurance software. The chapter then examines XP from this perspective, as a kind of case study.

[Simon Brown]

Sounds like an interesting chapter - one of the major contributing factors to project failure that I see again and again is because the team don't know and/or understand the development methodology that they're using.

As an aside, do you have any views on using agile methods in the context of more strategic enterprise-wide SOA projects?

[Scott Ambler]

Simon, you might be interested in some stuff that I have posted at the Agile Modeling and Agile Data sites, in particular Agile Architectural Modeling and Agile Enterprise Architecture. The EUP Enterprise Architecture Discipline might also be of interest.

BTW, Cliff and I will soon have an Agile Assurance and Agile Modeling article to share with everyone.

- Scott

[Simon Brown]

Excellent, thanks Scott, I'll take a look.