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 |
Introducing V1: Agile Team - ideal for small teams and teams new to Agile. Faster, easier and more powerful than a spreadsheet.
 |
Education:
Resources:
Events:
Join VersionOne at the Better Software Conference in Las Vegas. With a significant portion of the sessions dedicated to Agile development practices, this will be a great conference.
 |
The Agile Edge is brought to you by Valtech and VersionOne. This one day event will provide you with a world class framework for breakthrough performance and organizational transformation. Learn more at www.regonline.com/valtechagile.
 |
Partners:
VersionOne Partners are key leaders and consulting firms around the world that help companies successfully deploy agile development practices and processes. Learn more about how to become a VersionOne Partner.
 |
The role of the Scrum Product Owner is powerful, but challenging to implement. Success can bring a new and healthy relationship between customers/product management and development, even competitive advantage, but it comes at a price: organizational change is often required. In this article Roman Pichler looks at what it takes to succeed as a Product Owner.
In this interview taken by InfoQ's Deborah Hartmann during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book “The Art of Agile Development”.
A discussion about simple design is taking place on the extremeprogramming Yahoo! group that has already resulted in several useful recommendations. The discussion started off with a request for references concerning incremental design and quickly morphed into one about successfully adopting incremental design.
Since Linus Torvalds presentation at Google about git in May 2007, the adoption and interest for Distributed Version Control Systems has been constantly rising. We will introduce the concept of Distributed Version Control, see when to use it, why it can be better, and have a look at three actors in the area: git, Mercurial and Bazaar.
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
Segundo Velasquez came to the Agile 2007 conference to meet with an Agile team which promised him help to design and develop a web application meant to build a stronger relationship between Mano a Mano, a charitable organization, and its donors. Segundo shares his amazement on how quickly the whole process evolved.
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).
Agile communities consider stories “done” when the acceptance tests (also called story tests) are shown to the customer. Originally, this was a manual process, but in recent years, several frameworks have been created to automate this process, providing acceptance testing all the benefits of automated unit testing. One of the most popular of these if called FIT, created by Ward Cunningham.
At NFJS Venkat Subramaniam, author with Andy Hunt of "Practices of an Agile Developer," shared his pragmatic approach to some of the important technical and non-technical factors contributing to project success, including: coding, developer attitude, debugging, mentoring and feedback.
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.
