2/10/2012 by Jason Moccia
One of the myths of Agile software development is that documentation is not required or useful. It is true that one of the core values within the Agile Manifesto is "Working Software over Comprehensive Documentation." However, note the word "over"...
2/7/2012 by Elton Gao
Several weeks ago, I joined an online discussion about the key skills of an effective ScrumMaster. Everybody actively shared their experiences and thoughts. But I strongly felt that we were talking about the definition of a good ScrumMaster, not an effective one, which was the original topic.This made me recall an experience I had last year. I'd joined a new project that was outsourced, and...
2/7/2012 by Chia Wei Cheng
This is an article asking you to fail. More precisely: Fail now for greater success later.
One of the five Scrum values is courage. Courage to point out problems, ask for help, receive help, and — most important — take risks even thou...
2/2/2012 by Tushar Somaiya
Two words, Agile and coaching, seem to be the most-used buzzwords (after brain and neuro) of the last five years or so. The way things are progressing, I see them staying at the top of the list for decades.
1/31/2012 by Fernando Serrano
Quality: It's one of the common commercial arguments made when offering a software product. Those who have already mature products in the market justify their careers by emphasizing quality. Other companies, perhaps with more innovative products o...
1/30/2012 by Srinath Chandrasekharan
Agile, and Scrum in particular, are buzzwords. Everyone wants to try out Scrum and reap its benefits. Clients (especially business clients) see a big advantage in not having to wait till all the requirements are carved in stone before starting a p...
1/27/2012 by Madhu Venantius Laulin Expedith
When quality assurance teams and management who have adopted Agile practices first put the ideas to work, they face a significant impediment in unlearning the traditional mind-set and practices that experience in traditional practices has instilled in them.
1/26/2012 by Vadivelan Sivanantham
A widespread myth I've noticed in Agile software development is, "No documentation in Agile" or "Documentation is wasted effort." Particularly during a transition from Waterfall to Agile, we appreciate the benefits of adopting typical Scrum practices, such as short iterations, timeboxing, daily scrums, retrospective, and so on. We also try to get away from the tasks and activities that we found monotonous before Agile adoption — documentation, writing proper code comments, etc. But is it really correct to completely stop documentation and code comments?
1/25/2012 by Mark Stocker
I was at home a couple of Sundays ago, watching a Chelsea vs. Liverpool football match (soccer, for those Americans reading) — a match Liverpool ultimately won. It was during the post-match analysis that I was struck by some parallels between what Chelsea is going through and my own current client engagement to move from Waterfall to Scrum.
1/24/2012 by Satya Ravi Singh
I've always wondered -- not just as a developer but as a human being -- why I needed to follow the orthodox methods of typical hierarchical reporting. There was always some "middle man" confusing the conversation. You can define many roles in a typical hierarchical organization, and