Software Management with Scrum

First off, this post does not give and overview of Scrum, a very good case study can be found here (and an excellent book).

We decided to change our development standards at Scimatic.  After a lot of researching we decided to go with Scrum.  What I like most about the Scrum process is that you get an update from team members every day about what is going on.  Gone are the days where someone will wrestle with a problem for multiple days without input/help from team members.

We found a great software application for managing scrum projects called ScrumWorks.  We are currently using the basic version (which is free) and it seems to meet out needs so far.

The first project that we moved to scrum doesn't really fit the methodology too well as it is a small project.  We picked this project to evaluate scrum with because the sprints would be very short (1 week each) and it will give us some initial feedback very quickly if it is something that we want to use on bigger (and eventually all) development projects.

We finished our first sprint on Friday with a "shippable" build.  The first iteration went well, we found out quite early that we hadn't assigned enough work to fill the sprint.  After a couple of corrections along the way we found that the agile methodology is going to work well for us.

Overall, we are finding that software development with Scrum works well with very little management overhead.  The next test for us will be ramp up to a full project with Scrum.

Reply

The content of this field is kept private and will not be shown publicly.