Daily Scrum (first one!)

Now that TrailsWeb is a one person shop, it's hard to stay committed to specific goals amidst all the distractions of running a works worth of business in a single day.  I work four tens at the State of South Dakota making websites with maps on them.  That leaves me Friday to work at TrailsWeb all day, servicing the rest of its customers in one day each week.  I tried working Saturdays, too, but I burned out so hard I didn’t even want to think about coding after my forty hours at the state.

At the State of South Dakota, I was lucky enough to be the very first programmer to ever implement Scrum development.  Thanks are due, in large part, to my manager Adam Emerson who facilitated as Scrum Master.  The benefits of using Scrum on a large and complex project continue to emerge and I want to bring that same focused progress to my Moneylender Professional software.

A core part of scrum is the fifteen minute “daily scrum” meeting where these questions are answered by each member of the development team:  What did I do yesterday?  What do I hope to do today?  What roadblocks might prevent me from achieving this goal?

When answering an email asking about progress on Moneylender Professional 3, it occurred to me I could kill three birds with one stone.  I could write a “daily scrum” blog post every Friday morning with the details of what happened last week, what I’m working on now, and what might slow me down.  Customers can see the progress being made on the software and keep up to date as changes take place.  And the content I write will help Moneylender’s online visibility!

So, today’s daily scrum:

What did I do last week?
Last week I wrote an article for my Moneylender Blog about profitable outcomes with tailor made loans.  The week before I continued restructuring work on migrating MLP2 to the new file system in MLP3.  The new file system is a huge leap forward but requires system-wide rewrites to the application.

What do I plan to do today?
The main window of MLP is about 4400 lines of code.  Large parts of it must be rewritten to use the new file structure.  I would estimate that about five hundred separate revisions will have to be made application-wide for the program to compile so I can even begin to test it.  In the main window, the first batch of revisions involve create-, open- and close-portfolio code.  Today I would like to complete revisions on that code.

What roadblocks might prevent me from achieving this goal?
I have two phone calls to make to various clients that may lead to an hour or two of unrelated work.  One MLP customer is experience problems and may require ongoing support.  I want to write another article (albeit not as long as last week's) for the Moneylender blog.

That’s it for this week.  I’ll check in with updates and goals on the 9th.  Feel free to contact me with suggestions for features for Moneylender.  I maintain a “Product Backlog” now, which has a long list of desirable additions.  I order them based on the value they add to the whole user-base of the software.  All suggestions are welcome and will be recorded on the backlog.

No comments: