12/18/2014 by Robert Boyd
I often find that how work gets from the customer to the team is neglected or poorly understood. I would like to talk about this process and provide a framework for you and your organization to experiment with.
12/18/2014 by Kam Zaman
There has been much hype about Dual-Track Scrum, but not much about how it has been put into practice. I hope this post gives you some idea of how the concepts can be applied in your place of work.
12/17/2014 by Ebin Poovathany
Most of these organizations/teams later talk about the failure of Agile. I have heard many hypotheses about why this project is special and why Agile thinking won't work for this project. If we go a little deeper and examine the situation, we will see that they didn't transform the mind-set of the people involved.
12/17/2014 by Ravi Konduru
Looking at the increasing adoption rate of Agile and the rate at which organizations are heading toward Agile transformation, it is time to formulate a mechanism and a strategy to enable smooth Agile transitions.
12/16/2014 by SAVVY KATHAM
Your project is suffering from PODS -- Product Owner Disappearance Syndrome -- when the availability and commitment of the product owner is not enough to help teams complete the planned deliverables on time.
12/16/2014 by Rick Waters
There will always be memorable moments: post-sprint or project-wrap pizza parties, baby showers for team members (and their significant others), promotion celebrations, weddings, and going-aways. But how many truly proud moments are there?
12/15/2014 by Arun Kumar M
There are lots of tools and different types of frameworks available for using Agile in automation testing. Here we are going to look at QTP and SpecFlow integrated with Selenium or WatiN tools. . . .
12/15/2014 by JITENDRA SINGH GOSAIN
If a team has one bad iteration or sprint there is no need to panic; the team can use the retrospective meeting to see what needs to be changed, corrected, and improved in the next sprint.
12/12/2014 by Indhu KP
Do we really handle retrospectives in the way we are supposed to? . . . Retrospectives run the risk of becoming repetitive and boring, especially when (in the case of weekly sprints) they are conducted week after week.
12/12/2014 by Somashree Bhattacharya
Stand-ups happen, burn-down charts are in place -- and suddenly, toward the end of the sprint, things start falling apart. No matter how many times you meet or try to resolve issues, the comeback is never 100 percent. You have failed your sprint.