JetBrains recently announced the release of TeamCity 6.5. The new release comes with a new look and has improved integration with Git and Mercurial along with several improvements especially for .NET developers. Moreover the free Professional Edition now allows unlimited users.
Microsoft has unveiled at TechEd North America 2011 some of the new features coming in Visual Studio: more Agile tools for project planning and collecting stakeholder feedback, a connector for providing operations feedback to developers, plus architecture diagrams and unit testing for VC++.
SAP has recently introduced StreamWork as a cloud-based solution for collaborative decision-making. According to the German ERP company its product brings together the people, information, and proven business approaches to drive fast, meaningful results.
The privately owned US company Coverity claims that its newly released and browser-based software tool Coverity Integrity Control supports development organizations to set standard policies for code quality and security, and then manage, monitor and report on these policies as code is tested.
The latest version of Application Lifecycle Management (ALM) collaboration tool Tasktop supports task federation, cross-repository Agile planning, and new connectors to other ALM tools like HP Agile Accelerator and SmartBear CodeCollaborator. Tasktop team last week released version 2.0 of the software which also has integration with Hudson CI tool.
Facebook is probably the hottest company today, driving a very high level of interest and scrutiny. Despite a high level of secrecy, Yee Lee, a product manager at Skype, has assembled a large collection of notes detailing how code ships at Facebook.
Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over. Lacking time trainers (including this one) often race through the topic outlining only one simple type of retrospectives.
Angela Harms recently blogged about the Agile Retrospective Prime Directive. She discusses how the language of the prime directive around "everyone doing their best" could be seen as patronizing and insulting to team members. Other commentators who have discussed the intent of the Prime Directive include Esther Derby and George Dinwiddie. How useful is the Retrospective Prime Directive?
The Scrum Master job requires skills in diplomacy-- and effective communication. Team members must also communicate effectively. Tools for accomplishing these "soft-skill" tasks are now freely available. A detailed book about one of these useful tools entitled SOFTWARE FOR YOUR HEAD, is over 400 pages in total, and is now available-- free to the world in PDF format.
Agile has always stressed the need for an appropriate physical space to support the team and team practices. Ryan Martens recently wrote about the intersection of design, design thinking, and the agile environment - suggesting that open space and wall-to-wall whiteboards are just the beginning of what is needed to create an ideal agile team-space.
Cross functional teams are the teams in which all members work on delivery of the same business value. It could potentially be the same feature or the same product. Though, Agile recommends cross functional teams due to a lot of inherent advantages, there are some caveats that organizations need to be aware of.
This is the second in a series of discussions looking at factors that enable Agile teams to be successful. Diversity of gender, culture, opinion, perspective, skills and background is considered to be an important factor in forming and persisting high-performance teams. This news item examines the perspectives from variety of commentators.
This is the first in a series of discussions looking at factors that enable teams to be successful. This post reports on a recent Wired magazine article that looks at the creative process in use at Pixar Animation Studios and how their process encourages team formation, long-term relationships and trust in a “safe to fail” environment.
Agile projects are (should be?) highly collaborative team environments built on a foundation of trust and open, honest communication. Such collaborative environments don’t just happen, and they can be easily disrupted. There are many commentators who provide advice on how to establish and maintain collaborative teams. This article summarizes the advice from a few of them.
Change is constant, yet people fear change. It is mostly the fear of unknown and loss of comfort zones that makes the perception of a change painful. Though Agile teams are well prepared for change, however most of them are not comfortable when the change affects the team.