17. May 2009 18:19
In this post you will find my PowerPoint and source code I used for my presentation at Charlotte Alt.Net May meeting. I had a good time presenting this to the group even though it was very broad and shallow. I covered the basis on why you want to leverage tools and practices in a Lean Agile environment. I got into topics like Source Control, Unit Testing, Mocking, Continuous Integration and Automated UI Testing. Each of these topics could have been an entire 1 hour presentation on its own.
Here are the links to the tools that I talked about in the presentation:
Power Point “Tools for Agile Development: A Developer’s Perspective” http://www.protosystem.net/downloads/ToolsForAgileCharlotteAlt.Net/ToolsForAgile.ppt
NerdDinner solution with MSTests re-written as NUnit Tests and WatiN Automated UI Tests http://www.protosystem.net/downloads/ToolsForAgileCharlotteAlt.Net/NerdDinner_ToolsForAgileDev.zip
CI Factory modified solution that I used for creating a CI Build from scratch http://www.protosystem.net/downloads/ToolsForAgileCharlotteAlt.Net/CIFactory_ToolsForAgileDev.zip
12. July 2006 01:41
del.icio.us Tags: Scrum
On my flight from Charlotte to Phoenix this week I listened to a number of podcasts. One of my favorites is Hanselminutes. Scott Hanselman talks about a lot of thins I am interested in.
In the Line of Scrumage podcast Scott talks about applying the Scrum agile process in his work place. Most of what he talked about are things that we have been using at JDA Software Group Inc. However Scott brings up an interesting point about applying Scrum processes to a 1 person team. I have often thought about this for some of my own personal projects. I often do small projects for myself and I end up playing the roles of product owner, business analyst, developer, and tester. So could I effectively use Scrum as a way to manage these projects? Well I have sort of attempted this on a couple projects and here is what I found out.
The part about building a backlog of stories that are features to get into a product and giving them a priority is something that has worked for me vary well. I find it easier to express the features that I wish to get into my projects as a story. The story format lets me capture the user, action and benefit in a quick step. If I had to spend a lot of time working out the functional documentation of a given feature I am afraid I would not end up completing the feature in a timely fashion. Even prioritizing the features helps me focus on what needs to be developed next.
However the process of story pointing features and planning them out over multiple sprints just does not seem to give me any real benefit. The main reason for this is that since these projects are personal projects they do not get a consistent amount of time dedicated to them. I might have 3 hours 1 week and 0 hours the next to dedicate to the project. So planning for sprints and trying to determine my velocity is somewhat difficult. This aspect of Scrum ends up not being part of my personal projects. This is ok for me though because I feel more organized by maintaining a backlog with priorities.