|
|
Mon Nov 14 17:38:22 GMT 2011 processComplete agile from beginning to the end - http://agilewarrior.wordpress.com[..]com/2010/11/06/the-agile-inception-deck/ The methodalogic, and the development team you pick, affecting the process you have - http://www.leanessays.com[..]1/07/how-cadence-determines-process.html More process doesn't necessary solve all problems... in fact it may cause more problem - http://architects.dzone.com/news/process-not-working-must-have http://www.whattofix.com/blog/archives/2006/10/signs_you_have.php You might not be agile if. . . 1. The “Send/Receive” and “Save As” buttons initiate most team communication. 2. Your whiteboards are mostly white. 3. “Test-driven” still refers to your car. 4. You don’t yet know what PHB stands for. (It's the "pointy haired boss" in the "Dilbert" comic strip.) 5. You know that CPM stands for critical path method of project management, and continue to rely upon it. 6. You spend more time trying to manage project dependencies than remove them. 7. Someone still believes in the “Can’t Chart.” (Oops, that’s the Gantt chart.) 8. Developers only develop, testers only test, and managers just manage. 9. Simplicity is presumed to be simple. 10. A change control board meets . . . ever. http://www.versionone.net/Resources/AreYouAgile.asp http://www.jamesshore.com/Blog/Its-the-Software-Stupid.html (google search) (amazon search) second |