2015 in review

The WordPress.com stats helper monkeys prepared a 2015 annual report for this blog.

Here’s an excerpt:

A San Francisco cable car holds 60 people. This blog was viewed about 1,100 times in 2015. If it were a cable car, it would take about 18 trips to carry that many people.

Click here to see the complete report.

Star Wars – the force accounted

Recently a friend of mine sent me this, a link to Bloomberg’s article on Star Wars, or in particular, counting the number of times and length of anything to do with the Force in all Star Wars movies (till the upcoming one, of course).

force1

As a Star Wars fan and as a mathematician, this was a very nice exercise. I especially liked that they mapped the Force into specific abilities. This made me think about looking at these abilities and see whether I can map them to Agile.

force2

So here is my try to do just that – The force abilities and their Agile counterparts:

Sense: The demonstration of a heightened awareness of the world around the Force user. In Agile: The scrum master’s ability to sense and visualize that there is something wrong that needs to be fixed.

Force Leap: A preternaturally high or long jump, such as Luke Skywalker’s skyrocketing exit from inside a carbon-freezing chamber, or one that appears to require heightened physical awareness and balance. In Agile: The ability to take something that was said and project it to a totally different dimension, finding a solution from a distance.

Force Choke: The often-lethal constriction of another’s windpipe without physical contact, even at a great distance. In Agile: The ability to shut one’s mouth by going down on everything he said or believes.

Force Push: The projection of a moving energy field. In Agile: The ability to overcome obstacles by setting the aside, at least for a while.

Telekinesis: The movement or retrieval of inanimate objects (or droids) without physical contact. In Agile: The same as Force Push, overcoming impediments.

Jedi Mind Trick: The ability to influence the thoughts and behavior of others, using verbal suggestion. In Agile: The agile coaching on people that do not know Agile, is sometimes almost like a mind trick.

Telepathy: The purposeful sending of telepathic messages and the reception of such messages by living, sentient beings. In Agile: The ability to see where things are going, even before they happen.

Burst of Speed: This brief, swift sprint occurs quickly enough to create the illusion of disappearance. In Agile: The ability to be agile, to be quick and welcome change.

Force Spirit: This ability entails communication with the living by a deceased Force user, counted both when the manifestation is aural and when it is seen as a ghostly visual projection. In Agile: The ability to talk with the agile community, work with them and learn from the elders.

Force Lightning: The projection of intense, violent energy from the user’s fingers. In Agile: Well, couldn’t find something appropriate for this one. It’s a dark side trade anyway…

 

‘Star Wars: The Force Awakens’ Hits B.O. Tracking Boards: Current Opening Estimates At $185M-$210M

‘Star Wars: The Force Awakens’ Hits B.O. Tracking Boards: Current Opening Estimates At $185M-$210M
http://deadline.com/2015/11/star-wars-the-force-awakens-box-office-opening-estimate-1201636913/

Sent via BlinkFeed

Is Agile dead? I don’t think so. Part II

During my research on the subject of the “death of Agile”, I have encountered quite a few posts about the Crimson-guardproblem of abuse of the word “Agile”. [I must admit, and that’s even part of my “Star Wars – Agile – Dark side” theory (see So what is the dark side?), that indeed this is a problem. People are using “Agile”, “Agility” and even “DevOps” for ideas, processes and more that have little to do with the real concept of Agile. They are even doing it for their own private needs (money, power) and not necessarily just because they did not fully understand it (hence, they are “Siths”).]

These posts include Agile is dead. Long live agility where the author (one of the Agile Manifesto’s signatories) concentrates on this very topic, in which the word Agile is abused, and he promotes the use of Agility instead, hoping this would make a difference.

Another example is The Manifesto is ancient history. Agile is alive and changing where the author writes about the meaning of the word Agile.

Though this discussion is very interesting, and often raises clarity on some of the topics, and although I already admitted that this is indeed a problem, I must say that this has nothing to do with the ‘death of Agile’. Even if the word is misused, even if there is vagueness around the differences between the Manifesto and Agile (and even Agility), this just comes to show that we need to be more clear about our terms and thoughts, and has nothing to do with whether these ideas and terms are still alive, still have meaning and still work.

The real discussion should be whether Agile and the manifesto are here to stay, or whether there is a need to do something else. This and more, in my next post on the subject.