Tracking change and innovation in the enterprise software development community
Testing Tools to
Support Agile
Software Delivery
Whitepaper
Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD). The presentation intends to be a primer for managers who want to understand the value of TDD, and of Agile in general, in software development.
Microsoft has created a new server, called Windows Essential Business Server 2008 (EBS), which combines management, messaging and security features into one integrated multi-server solution. The new server is targeted to midsize businesses with reduced IT staff personnel of 1 to 3 persons.
Is the role of an agile manager only that of servant leader? Should they ever use traditional command and control tools? Should the agile manager ever wield authority and make demands of the team? Should they ever make changes in the membership?
In team sport, as in software development, the team factor is crucial for success. In fact, team sport shows many inspiring parallels to software development. This article outlines 9 essential principles top-coach Marc Lammers discovered while building the world’s best field hockey team, and maps them to software development practices
It's an old story. Techies cave in to the business guys because they don't know how to push back. The problem? Developers use numbers primarily for computation, but the business uses numbers to make decisions. In this story the "Spirit of Agile" encourages a developer to turn non-computational problems and issues into number language.
In this talk filmed during Agile 2008, Jim McCarthy talks about 11 commitments team members should adhere to if they want to achieve a state of shared vision. Such a state empowers a team to reach their full potential and ultimately attain greatness.
Joseph Pelrine was present when XP took its first steps, was Europe's first Certified Scrum Trainer, and today is still breaking new ground. In this 2007 InfoQ interview, Joseph talked about Network Analysis and how Social Complexity Science informs his work with teams; the usefulness of the Dilbert archetype; & a speed-dating technique to help teams get started (creating software, of course).
Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.
Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, former Chief Engineer at Toyota, and the lessons he learned from him.
