The Artima Developer Community
Sponsored Link

.NET Buzz Forum
Scrum Software Methodology

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Jonathan Crossland

Posts: 630
Nickname: jonathanc
Registered: Feb, 2004

Jonathan Crossland is a software architect for Lucid Ocean Ltd
Scrum Software Methodology Posted: Feb 5, 2009 4:39 AM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Jonathan Crossland.
Original Post: Scrum Software Methodology
Feed Title: Jonathan Crossland Weblog
Feed URL: http://www.jonathancrossland.com/syndication.axd
Feed Description: Design, Frameworks, Patterns and Idioms
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Jonathan Crossland
Latest Posts From Jonathan Crossland Weblog

Advertisement

Scrum is an Agile Software Development Process that Jeff Sutherland invented based on work done at Easel Corporation in 1993.

Pigs and chickens?

A very quick overview. A Scrum Master, leads the scrum. Typically a scrum meeting should be a precise meeting, standing and ready to leave after 15 minutes.
With precise questions:
1. What have you done since yesterday?
2. What are you planning to do by today?
3. Do you have any problems preventing you from accomplishing your goal? (It is the role of the ScrumMaster to remember these impediments.)

Each iteration is called sprints, and are typically 4 weeks of development. I have found that usually you end up writing code for 2 weeks, integrating and testing for a week and fixing it up a bit before the sprint ends. Not sequentially, but more something like this
code, test, code, integrate, test, code, deploy, code, test, deploy

Each sprint has a design and a plan. You set out the goals of the sprint, and then you sprint, with your 15 minutes of meeting each day. So it is not blindly sprinting. As that, could cause injury.

Testing is part of it, and unit testing is critical.

Have a look at Control Chaos for information on SCRUM.

When you are ill, you visit Doctor

And when your project is ill, you should call a qualified Agile practitioner.

If you project is running late, and you don't use any Agile Methods, "SCRUM and XP" together for a few months, will more than likely help the situation.
However, I should stress, if you are new to these methods, don't try it on your own for a critical project. Get a consultant, get someone who knows the method, who you can work with your project team, who can help you implement the 3 months properly.
The team ethic, the calculated sprints, unit tests and pair programming are definitely a great combination for a lagging project.

One of my favorite things about scrum is the burn down chart.

When other methods, like Waterfall demand more documentation and quantification in time consuming ways, this is simple and very visual. it is as accurate as any other, as its still prediction at the core.

I am going to be asking Kent Beck, about XP, and maybe, just maybe (I am trying) to get Jeff Sutherland on as well for a word on SCRUM.

Next post, DSDM. (If you are in a very formal method, DSDM could help, as it offers the most structure to Agile Methods?)

Read: Scrum Software Methodology

Topic: Artikel: WPF Erneuert Previous Topic   Next Topic Topic: Windows 7 Editions announced

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use