|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 8
Messages: 8
Messages: 8
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Scrum and XP from the Trenches
Henrik Kniberg has put together a ninety page PDF called "Scrum and XP from the Trenches," with Scrum described as "an agile method for project management" on Wikipedia (see "Scrum (management)" and "Scrum (development).") This paper details what Mr. Kniberg found to work for him at his (unnamed) client, "the result of one year's Scrum experimentation in a development team of approximately 40 people."My current approach to Scrum is the result of one year's Scrum experimentation in a development team of approximately 40 people. The company was in a tough situation with high overtime, severe quality problems, constant firefighting, missed deadlines, etc. The company had decided to use Scrum but not really completed the implementation, which was to be my task. To most people in the dev team at that time, "Scrum" was just a strange buzzword they heard echo in the hallway from time to time, with no implication to their daily work.
Over a year's time we implemented Scrum through all layers in the company, tried different team sizes (3 12 people), different sprint lengths (2 6 weeks), different ways of defining "done," different formats for product backlogs and sprint backlogs (Excel, Jira, index cards), different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. We also experimented with XP practices different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum.
This is a constant learning process so the story does not end here. We learned a lot in a year, yet I'm convinced that this company will learn just as much next year (if we keep up the sprint retrospectives) and gain new insights on how to best implement Scrum in this particular context. He poses the paper as a "war story," to help "turn Principles and Practices into... well.... How Do You Actually Do It." He describes Scrum in quite a bit of detail:The product backlog is the heart of Scrum. That is where it all starts. This is basically a prioritized list of requirements, or stories, or features, or whatevers. Things that the customer wants, described using the customer's terminology.
We call these backlog items today, but in the future we'll probably start using the XP term stories instead. Our backlog items include the following fields:- ID a unique identification, just an auto-incremented number. This is to avoid "losing" items when you rename them.
- Name a short, descriptive name of the backlog item. For example "See your own transaction history." Clear enough so that developers and the product owner understand approximately what we are talking about, and clear enough to distinguish it from other back log items. Normally 2 10 words.
- Importance the product owners importance rating for this item. For example 10. Or 150. High = more important.
- I tend to avoid the term "priority" since in many cases priority 1 is considered the "highest" priority, which gets ugly if you later on decide that something else is even more important. What priority rating should that get priority 0? priority -1?
- Initial estimate the team's initial estimate of how long this will take to implement. The unit is "ideal man-days, with ideal team size." Ask the team "if you can take the optimal number of people for this job (not too few and not too many), and lock yourselves into a room with lots of food and work completely undisturbed, after how many days would you come out with a finished, demonstratable, tested, releasable implementation?" If the answer is "with 3 guys locked into a room it would take 4 days" then your initial estimate is 12 ideal man-days.
- We will probably start calling the unit "story points."
- How to demo a high-level description of how this backlog item will be demonstrated at the sprint demo. This is essentially a simple test spec. "Do this, then do that, then this should happen."
- If you practice TDD (test-driven development) this description can be used as pseudo code for your acceptance test code.
- Notes any other info, clarifications, etc.
It's an excellent document, serving as an adequate introduction to XP and Scrum - and as he says, if you find an element that doesn't work for you, you're quite able to change it to fit your requirements.
|
|
|
Message #223020
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Well worth a read ...
Excellent article , well worth a read for anybody experience pain on their project (especially as the delivery deadline approaches) and wondering how they can do better next time.
What gives it most weight is that the author is not 'in your face' about trying to sell you something (some whitepapers from Rational come to mind here). Unless of course you're in the market for OO consulting and happen to be based in Sweden ...
Even if you're not into Agile / Scrum / XP there's enough in here to convince you (or your boss) to give it a go.
Paul , Technology in Plain English
|
|
|
Message #223041
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Scrum and XP from the Trenches
I concur with the previous poster. Excellent article!
Sent a link to the PDF to a colleague who does not have much experience of Agile methodologies, but is curious. I think he was quite excited about the article.
|
|
|
Message #223045
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Scrum and XP from the Trenches
Excellent paper. Echo many of the experience and lessons learned from my team.
Chester
|
|
|
Message #223086
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Scrum and XP from the Trenches
Thank you Henrik. That was a really great paper filled with a lot of useful content.
|
|
|
Message #223189
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Scrum and XP from the Trenches
Excellent article. Seems like truly from the trenches. I use monthly sprints and use Wiki for that purpose. There two issues that I seem to grapple with are 1) Wide gap between actual and estmated velocity, especially during the early volatile stage in a project. What should be the window of average past velocity to use for next estimated velocity. 2) As far as the tech items as the author calls them, although ideally they should be tied to a user story, sometimes it's not possible. You are forced to create kind of a "tech story"
Pranab
|
|
|
Message #293804
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Scrum and XP from the Trenches
I've read this book at once. It's very nice when people who have wide practical experience share it with others.
My team had been using several Scrum practices very similar to those described in the book.
But I prefer to keep task board as simple as it possible. So our approach to planning is much more easier.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman continues to explore the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(January 21, Article)
Ted Neward is an independent consultant specializing in high-scale enterprise systems, and an authority in Java and .NET technologies. He is the author and co-author of several books, including Effective Enterprise Java. At TheServerSide Java Symposium in March, he will be presenting sessions on pragmatic architecture, ECMAScript and Scala.
(January 15, Article)
Now that Oracle is absorbing Sun Microsystems, there mixed views on what should come of the Java Community Process (JCP). While some say Oracle should become the new steward of Java and keep the JCP much as it was, others argue that it may be time to open-source this widespread language.
(November 24, Article)
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
