We are a middle-sized organization of coaches, consultants and developers – and we see ourselves Agile and Lean through and through, to the core, dyed-in-the-wool, born-and-bread. Well, to be honest, we might be not. Or at least not from the beginning. Over the years, we learned a lot: * How to have self-organizing teams * How to manage our acquisitions and changes with Kanban boards * How to improve our communication with social media * How to distribute power and responsibility in a company owned by their employees And we’re not done learning yet. ...

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.

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 e ...

This article focuses on the obstacles to using Agile in a distributed team environment and recommends how to counter them with what is called “de-Agile.” De-Agile is tailoring Agile to fit your team by taking out processes that don’t make sense and tweaking those that need to be modified to suit your needs. In a distributed team environment, de-Agile is mostly about removing the sense of being distributed. You need to educate each team member about the additional communication responsibilities required when working with remote team members and emphasize the ...

Does the term “documentation” have any place in an agile environment? The goal on agile projects is to keep documentation as simple as possible, relying on roadmaps, overviews and concepts rather than enterprise-focused details. But what happens when using an agile approach on more complex projects? For example, what if the team that writes the software is different from the team that must maintain it? Or what if auditors come calling? In these instances, basic agile documentation based on user stories alone may come up short. This article provides insights ...

Lexington, MA, January 31, 2012- AccuRev, Inc., the leading provider of advanced tools for managing the software development process, today broke new ground with the release of the first Git integration that seamlessly bridges the world of open source and commercial tools for enterprise-class softwa ...

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...

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...

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 archite ...

This article discusses estimation techniques for teams that are adopting Scrum. The authors recommend to use story points during the release planning phase, but initially to switch to hours to estimate tasks during the sprint planning. Then the team will gradually move to using story points to estimate complete stories that members will commit for in next sprint.

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.

David Horton of Citrix Online will be the guest speaker at the Los Angeles Agile Project Leadership Network Quarterly Networking Event in Los Angeles, California on February 7, 2012. The Los Angeles Agile Professional Leadership Network (LAAPLN) is kicking off 2012 on Tuesday, February 7, 2012 at 6PM, with David Horton of Citrix Online. David will give a real-world example of implementing and using Agile and Scrum in an Enterprise environment.....

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 Doma ...

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.

This video tells the story of a project that was in a bad shape after a first waterfall attempt and 2 months of Scrum that failed to deliver any working code. This talk shares the technical practices adopted and how they evolved but mainly focuses on what it took to make the project work in a big organisation with the typical command-and-control mindset It discuss attitude and culture of people on the team and how our values worked against the values exhibited by other teams. Video Producer: http://agilece.com/

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

The new version v6.50 of freeware tool Sprintometer for Scrum and XP project management has been released on Jabuary 21, 2012. Everybody knows Sprint Burn down chart used in Scrum projects but very often managers need to know situation with the whole agile project and specifically they are intereste ...

The new version v6.50 of freeware tool Sprintometer for Scrum and XP project management has been released on Jabuary 21, 2012. Everybody knows Sprint Burn down chart used in Scrum projects but very often managers need to know situation with the whole agile project and specifically they are interested in Project Burn down chart. New version of Sprintometer allows this! How it works: go to tab called ‘Scope Chart’ on project level and enter percentage for already estimated sprints in relation to the whole project scope. Sprintometer will automatically generate Burn down ...

Monrovia, CA – January 24, 2012 Parasoft Corporation, industry leader in automated defect prevention and detection, today introduced a new release of Parasoft Jtest: the industry's most comprehensive Java testing solution. Parasoft Jtest automates static analysis, unit testing, coverage an ...

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?