InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

InfoQ Book: Scrum and XP from the Trenches

Posted by Floyd Marinescu on Jun 29, 2007

Sections
Process & Practices,
Architecture & Design
Topics
Agile ,
Methodologies
Tags
Scrum ,
XP

Henrik Kniberg last year published wildly popular paper 'Scrum and XP from the trenches' in which he chronicled in pictures and text how his 40 person development team implemented parts of Scrum/XP over a one year period.  Henrik has updated his work and published a new version of it as a full book with InfoQ.com. 

Henrik's team experimented with different team sizes, different sprint lengths, different ways of defining "done", different formats for product backlogs and sprint backlogs, different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. They also experimented with XP practices - different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum.

Download Scrum and XP from the Trenches. The 168 page book is also available for purchase for $22.95.

The book includes:

  • Practical tips and tricks for most Scrum and XP practices
  • Typical pitfalls and how they were addressed
  • Diagrams and photos illustrating day-to-day work
  • Testing and test-driven development
  • Scaling and coordinating multiple teams
  • Dealing with resistance from inside and outside the team
  • Planning and time estimation techniques

Henrik Kniberg is a consultant at Crisp in Stockholm specializing in Java and Agile software development; he has founded several Swedish software companies and is passionate about learning, teaching, and applying the art of software development. Henrik takes a holistic approach and enjoys adopting different roles such as manager, developer, scrum master, teacher, and coach.  Thank you Henrik for making this book available to the community!

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Thanks for making this available! by Michel Löhr Posted
thanks by asdfasdf asdfasdfsadf Posted
Re: thanks by Deborah Hartmann Posted
Book == Paper by Tammy M Posted
Re: Book == Paper by Henrik Kniberg Posted
Suggested name change by Curt Hibbs Posted
Re: Suggested name change by Henrik Kniberg Posted
  1. Back to top

    Thanks for making this available!

    by Michel Löhr

    I have already read the first version which provided a lot of value. I will definitly read this one as well.

    Again my thanks!

  2. Back to top

    thanks

    by asdfasdf asdfasdfsadf

    i am student,this book is useful for me. thanks

  3. Back to top

    Book == Paper

    by Tammy M

    Hi

    I read this paper some ago and loved it. What I can't tell is... Is this book an expansion on the original paper or simply a nicely printed version of the same? I went to lulu.com where the book is sold and the preview for the book is a generic preview (guess they forgot to replace it with a preview of the real book).

    Does anyone know if this book expands on the paper? I would certainly buy it if so. The paper is quite good.

    thanks
    t

  4. Back to top

    Re: Book == Paper

    by Henrik Kniberg

    It's mostly the same content, I just added some corrections and clarifications. And of course the forwards by Mike Cohn and Jeff Sutherland.

    Many people have asked for a printed version, since it is more comfy to hold a real book in your hand than to read over 100 pages on a computer screen. The InfoQ solution caters to both tastes - those that prefer a free version that they can read on screen as well as those that prefer paying a small fee to receive a physical book.

    /Henrik

  5. Back to top

    Re: thanks

    by Deborah Hartmann

    Hello asdfasdf

    I'm glad you find it helpful.

    We're pretty friendly here :-) please consider using your real name in your registration profile! It makes comments more meaningful.

    Thanks!
    deb

  6. Back to top

    Suggested name change

    by Curt Hibbs

    In the section "How we prepare for sprint planning", you explain the meaning of the "Importance Rating". In effect, this is a ranking, not a rating. So I would suggest just using the term "Importance Ranking" to more closely match its actual meaning.

  7. Back to top

    Re: Suggested name change

    by Henrik Kniberg

    Good point. Thanks for the suggestion! /Henrik

Educational Content

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?