To: numberonepal
My biggest issue as that business requirements never have a cutoff because Agile. The entire release cycle has to be Agile for it to properly work. I'm not sure it can EVER work in an Enterprise environment, however. It always turns waterfall-ish in the end. Correct. Technically when requirements change, all work should be reset and put in the next iteration for agile to work. But many people do not do that and just end up violating age old project management rules.
To: KC_Conspirator
I have found that we spent more time doing the PROCESS of agile than the software we were trying to make
In the end I often just gave up and wrote the stupid thing
47 posted on
04/18/2017 7:39:21 AM PDT by
Mr. K
(***THERE IS NO CONSEQUENCE OF OBAMACARE REPEAL THAT IS WORSE THAN KEEPING IT ONE MORE DAY***)
To: KC_Conspirator
...all work should be reset and put in the next iteration for agile to workUr funnie!
53 posted on
04/18/2017 8:08:46 AM PDT by
numberonepal
(First they came for Sarah, then they came for Herman, and now they've come for Trump.)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson