Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
Originally posted by Scott Ambler:
You might find The Agile Unified Process (AUP) to be an interesting instantiation of the RUP.
[OCP 11 Complete Study Guide] [OCP 11 Programmer I Book] [OCP 11 Programmer II Book] [OCP 11 Practice Tests Book] [OCA 8 Book] [OCP 8 Book] [OCP 8 Practice Tests Book] [Blog]
Originally posted by Scott Selikoff:
if you have a team that is already proactive [an agile process] is not really neccessary and can be burdensome.
Originally posted by Scott Selikoff:
Alternatively, if you have a team that only does the bare minimum and never really looks ahead or considers the consequences of their actions, then [an agile process] is a winner.
Originally posted by Scott Selikoff:
others, I feel [an agile process] just gives them another way to seem productive without being so.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Scott Selikoff:
I've done the agile process before.
I find that what it really does is encourage team members to be proactive, ergo if you have a team that is all ready proactive its not really neccessary and can be burdensome.
I've seen that for some people its an enlightening experience that forces them to become more proactive then they were before, others, I feel it just gives them another way to seem productive without being so.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
[OCP 11 Complete Study Guide] [OCP 11 Programmer I Book] [OCP 11 Programmer II Book] [OCP 11 Practice Tests Book] [OCA 8 Book] [OCP 8 Book] [OCP 8 Practice Tests Book] [Blog]
<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
[OCP 11 Complete Study Guide] [OCP 11 Programmer I Book] [OCP 11 Programmer II Book] [OCP 11 Practice Tests Book] [OCA 8 Book] [OCP 8 Book] [OCP 8 Practice Tests Book] [Blog]
Originally posted by Scott Selikoff:
Perhaps, although I merely bring them up to point out that agile is not fool-proof, as in any methodology. I'm sure there are companies out there who've adopted agile that have done far worse, despite the credos of the philosophy.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Scott Selikoff:
The first example of Agile being negative: This is partially related to management who took the notion that there should be daily 10 minute check up meetings to mean that we should have 30-60 minute 8am meetings every single day. The whole concept of the meetings was short, brief, and really only as required. Coming in an hour early to sit around while people talked for up to an hour didn't really increase my productivity.
The meetings are really only to encourage people who waits weeks at a time to report problems to others to come forward quicker and get help. If you spend a good amount of time walking to people's desks and handling problems as they come, the meetings aren't as important.
I've seen people waste *hours* discussing Agile philosophies pretending as if they were getting work done... no make that *days*.
Oh and one note, we implemented Agile in proof of concept scenario without having customers or requirements analysts...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |