Tracking change and innovation in the enterprise software development community
Content in this box provided by our Sponsor:
 |
VersionOne, recognized by Agile practitioners as the leader in Agile project management tools that streamline and standardize software development. By simplifying the process of planning, tracking and managing Agile software projects we help development teams consistently deliver software faster.
V1: Agile Team |
Stop using spreadsheets and cardswalls to plan, track and deliver software development projects. V1: Agile Team is faster, easier and more powerful, helping single teams quickly get started with Agile. Learn more !
 |
Survey:
Education:
Resources:
Partners:
VersionOne is dedicated to helping our partners grow their businesses. VersionOne Partner benefits include – financial rewards, client rewards, easy participation and free membership. For a limited time, joining the VersionOne Partner Community is even more rewarding. Join now and receive 50% referral incentives on your top VersionOne leads!
 |
Events:
Join VersionOne at the APLN Leadership Summit in Seattle. Attendees will collaborate with experts to find solutions and new directions for leaders in the Agile space.
 |
VersionOne is excited to be sponsoring Agile 2008, the premier international conference in Agile development. Learn more about the latest techniques, technologies, attitudes and first-hand experiences for successful Agile development.
 |
Ryan Cooper reviewed Amr Elssamadisy's new book and found it a useful framework for designing customized adoption strategies. Rather than a single recipe of Agile practices for everyone, the reader is offered patterns and tools to help determine which practices will most effectively help them reach their own organization's specific goals.
Agile software development can be done effectively with the help of right tools for the job. Kent Beck, recently published a paper exploring the relationship between tools and Agile software development.
The second Agile Alliance Functional Testing Tools Workshop is being held the day before Agile 2008 (Monday August 4). This is the second workshop being held this year and its goal is “advance the state of the art of automated functional testing tools used by Agile teams to automate customer-facing tests”.
In comparison to Java, an emphasis on continuous refactoring is still relatively new in .NET. Besides having few ardent proponents, many myths linger around what refactoring really is and how it applies to the development process in general. Danijel Arsenovski, author of Professional Refactoring in Visual Basic, attempts to dispel some of these myths.
Feature teams, common enough in small groups, are all too rare in large product development - but they can be a key to scaling with agility. This article analyses how feature teams resolve weaknesses of component teams, and points out key issues to address when transitioning. It is an excerpt from "Scaling Lean and Agile Development," by Craig Larman and Bas Vodde, to be published later this year.
In this interview made during Agile 2007, Dr. Hakan Erdogmus, Editor in Chief of IEEE Software, discusses about TDD starting from a study done by Ron Jeffries and Grigori Melnik and published as "TDD--The Art of Fearless Programming" in the IEEE Software magazine. Hakan talks about current misunderstandings regarding TDD's role in software development and the adoption issues it faces.
In this interview taken by Deborah Hartmann during Agile 2007, Rachel Davies, director of Agile Alliance, talks about Generic Agile, about the necessity to understand what is important in a development process, rather than sticking with a strict Agile method.
In this presentation filmed during Agile 2007, Stacia Broderick introduces Agile to traditionally trained project managers by making a comparison between Project Management Institute's (PMI) best practices and their equivalent Agile techniques.
A retrospective on Google's first Scrum implementation. Jeff Sutherland visited Google to do an analysis of the first Google implementation of Scrum on one of their largest distributed projects. Their strategy for inserting Scrum step by step into the Google engineering teams showed great insight and provides helpful lessons learned for all Agile teams.
For those getting started with Agile, this book offers a detailed first-person account of how one Swedish company implemented Scrum and XP with a distributed team of 40 people, and how they continuously improved their process over a year’s time.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
Domain Driven Design is a vision and approach for designing a domain model that reflects a deep understanding of the business domain. This book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.
Scrum, arguably the fastest-growing Agile methodology, is well described in the original Scrum books, which tend to be read once and put aside. The SPRiNT-iT coaches have abstracted the basics to produce a compact reference to help teams facilitate all Scrum meetings and create the Scrum artifacts. The book doesn't teach Scrum, but offers trained teams confidence to run their first successful Sprints - successes that will increase the acceptance of Scrum in their organization.
