Productivity

Agile, agile, agile. In the software development world, the word’s becoming impossible to ignore. Every day sees another dev team decide to "go Agile," and technology research and advisory companies are placing "agile development practices" as one of the four key components in their analysis.  Often, this leaves testers and managers in a traditional "QA" department looking around wondering just what their new role will be. Right after "Agile means no documentation," one of the next most-frequently seen myths is that Agile teams only need to include a product owner and some developers — no testers required — the developers ...

In a perfect world we could have anything we want. And that goes with our professional perfect world as well. And in terms of project management, that would mean we could pick what we manage, when we manage, who we manage, what customers we manage projects for, how we manage, what processes we follow and to whom we report project information. Total freedom. As an independent consultant, you get some of those freedoms, but you are still accountable and if you think otherwise, then you’ll soon find yourself with lots of time on your hands and no clients to perform ...

Unlike traditionally run projects which are planned by an “expert,” Agile planning should be done with the entire team participating. Agile encourages group participation in all forms of planning and estimation. Instead of one person following a linear process of assessing requirements and project constraints, then producing a plan designed to drive schedule, budget, and resources to deliver the end project, the whole team is engaged.

Enhance user experience by adding interactivity to your reports using Telerik Report Designer.

In this short tutorial you will find out how to integrate the OpenAccess ORM Enhancer, injecting the change tracking functionality, in your NAnt build process.