Although Agile processes are being used increasingly in many software development environments, some enterprises still haven’t adopted Agile because of various concerns, especially about using it with distributed teams. In this article, I focus on the obstacles to using Agile in a distributed team environment and recommend how to counter them.

In the Sungard Front Arena, current software portfolio a business functionality called Market Server Capability (MSC) is embedded and duplicated in many components. By the application of Agile and Lean principles on model-driven development, we will get an Agile approach for constructing the architecture of a new MSC definition which will eliminate the duplication and inconsistency, while still maintaining a short implementation phase. The resulting architecture has a single modeling level, with merged PIM and PSMs. The model is designed by reverse engineering of the legacy code in a Test Driven Development fashion.

We executed our project in a Scrum manner without even knowing our method was Scrum. What initially looked like an impossible project was delivered in six months, with exceptional customer satisfaction and confidence all around.

Mockery is a simple yet PHP mock object framework for use in unit testing with PHPUnit, PHPSpec or any other testing framework. Its core goal is to offer a test double framework with a succint API capable of clearly defining all possible object operations and interactions using a human readable Domain Specific Language (DSL). Designed as a drop in alternative to PHPUnit's phpunit-mock-objects library, Mockery is easy to integrate with PHPUnit and can operate alongside phpunit-mock-objects without the World ending.

This free online tool provides simple service that allows you to create and edit your Scrum burn-down charts.

Dealing with a large amount of user stories (more than your fingers and toes can account for) is not easy, most often they sit one after the other in your product backlog, or they are shuffled on a story map.

There is no such role as project manager in Scrum. But there are project managers in the organization. So what is the project manager supposed to do when the team is transitioning to Scrum? The easy part is that this question has already been asked and answered so many times. The hard part is that the answers are different and sometimes contradict each other.

The Burndown chart is very simple. It is easy to explain, easy to understand. But there are pitfalls observed in many agile workshops and adoptions. People tend to think the Burndown chart is so simple they do not give appropriate attention to understand what it says.

It's difficult to change learned behavior, and even harder to change group habits. This is one reason why it is difficult establish Scrum Most companies understand that Scrum has a lot of potential and bears the chance to shorten time-to-market or the delivery of high-quality software, but. . . . And there we go again: "Scrum, but. . . ."

"Agile testing" is not a completely different testing procedure but a software testing practice, following the principles of the Agile life cycle. How? Its most salient aspect is that it emphasizes testing and close work with the end users or at least with the story owners throughout the project.