Re: [AM] Too ambitious?

Steven:

But think of the opportunity!

Aside from displacing the current culture with an agile approach, which is 
sometimes the most difficult part, understanding what the "agile" in agile 
modeling really means and conveying that to the team members and stakeholders might 
be your most significant task. Teams that have been using traditional 
development methodologies in traditional team structures and processes often have a 
difficult time adapting to agile methods. 

From my perspective, the use of templates to build a new product should not 
pose undue liability, particularly if the new system is intended to be similar 
in some way to existing systems (for continuity in appearance, maintenance, 
etc.). I have been using a similar approach to building application systems and 
products using what might be called a "dynamically customizable  system 
template" for quite some time, and it has worked very well for both me and my 
clients.

One thing I'd suggest for sure is that you keep in mind is that agile 
modeling is not about new and excitng development tools, exotic programming languages 
or the latest and greatest "best practices" techniques, it's about people and 
process. I sometimes describe it as a "state of mind". To paraphrase 
(somewhat poorly) a current television advertisement for a chemical company: "Agile 
Modeling doesn't build software, it makes building software better".

Good luck in your new venture, and keep us posted on your progress.

Regards,

Pete 

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

For Topica's complete suite of email marketing solutions visit:
http://www.topica.com/?p=TEXFOOTER
--^----------------------------------------------------------------