|
Does anyone actually perform Agile the way it was intended?
We are an Agile(ish) shop and it works for us. We are not strict Agile per the definition(s), but we have borrowed key features and we strive to stick with that.
15 signs you’re doing agile wrong | InfoWorld[^]
|
|
|
|
|
The team in the office next to mine does, and it works* exceedingly well for them.
*I had a long chat with their team leader, I think he can make any methodology work because he is a good team leader period. He just finds Agile more intuitive than other methods.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
15 signs you're doing agile wrong?
You just know that whatever is past its best when pundits start to write articles like that.
It's a bit like "10 signs of a failing company" by the ex CEO of Toshiba Tsuyoshi Kawanishi; and he should know.
|
|
|
|
|
First company I worked for used the A.N.A.R.C.H.Y. methodology, wich stands for Anarchy Reigns Supreme And Chaos Will Follow.
Then I worked as a consultant for a notorious manifacturer of unreliable cars powered by spaghetti and they used the M.I.C.R.O.M.A.N.A.G.E.M.E.N.T. methodology, which I can't say what it stands for because they only organized 941 meetings and are still undecided if the second letter is "Incompetent" or "Insane".
Thne I worked for a customer who was moody and remembered crucial details on the day of the release... the work was basically Extreme Programming even if it had no designation managed by a competent manager so it went smooth.
Now I'm working AGILE like anybody else does: not AGILE at all, too many meetings with a developement team sparse in 3 nations and 3 US states. The new manager seems competent and experienced though and she is striving to put some process control in all of this.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Also great and used extremely unsuccessful by my previous employer: "Pippi Langstrumpf Prinzip" (german description of the principle: [^] )
Translated: "Pippi Longstocking principle"
Most important feature: I make the world as I like it.
How to use most efficiently: Every (cross-department) team member makes his own rules, especially concerning if one´s responsible for some current issue. Department leaders of (cross-department!!) team members hate each other and use every opportunity to shoot each other. I loved it
Then upper management introduced a new middle manager who brought some of your M.I.C.R.O.M.A.N.A.G.E.M.E.N.T. into the game. He got some further than your discussions: C stands for "Crap" and T for "Torture your employees". Of course I had to visualize those points excessively so he could present it to upper management.
Unfortunately I found some new opportunity and had to suddenly leave
|
|
|
|
|
|
spaghetti method works for me. I just start writing code and then, after a day or 2, take a look at what was wanted.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|