Scrum Thoughts
Paul Clerkin
Websites
Calendar
|
July '09 | |||||
| Mo | Tu | We | Th | Fr | Sa | Su |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Syndicate This Blog
References
Referring links
- www.local.ie[2]
Recent Entries
On the road again
Scrum Thoughts
Calling Names
A long time ago, in a far away place....
A great week for Irish architecture
Wednesday, December 3 2008
Scrum Thoughts
Wednesday, November 19 2008
Calling Names
Thursday, November 13 2008
A long time ago, in a far away place....
Thursday, November 6 2008
A great week for Irish architecture
Monday, November 3 2008
Twitter Updates
follow me on Twitter
Wednesday, November 19. 2008
Scrum Thoughts
I was at a talk last night, billed as a Scrum 101. Not familiar with the process, but having heard the term a few times recently, I went along. It was quite interesting, and suited if not was largely already my mode of working.According to Wikipedia: "Scrum is an iterative incremental process of software development commonly used with agile software development.... Although Scrum was intended to be for management of software development projects, it can be used in running software maintenance teams, or as a program management approach."
When faced with either a huge backlog of new additions or content, I approach it this way.
- Create a list and prioritize tasks - what is the most valuable addition to the site?
- Decide what can be completed this week, this is my "sprint" - I have to keep rolling out new areas, so I break down larger parts of the projects into small manageable parts. Usually this entails one larger area, and a handful of smaller ones than can be completed in an evening, with the larger segment being spread over the week.
- Tackle them
- Deliver (ie upload), usually on a Thursday evening.
Now I work alone, so it's not quite the same as the classic Scrum methodology but it's not that far off.
Currently for example I have a huge array of written content to cross-link and illustrate. When I say huge, it's going to be five or six hundred pages, easily the biggest new single area added in some time. I recently uploaded a new area for the UK - spread over several weeks, I kept delivering new pieces or versions until completion. That will be my approach with the Irish content.
Sadly because I work alone, I don't have the daily scrum meetings, it would be too strange....
- Create a list and prioritize tasks - what is the most valuable addition to the site?
- Decide what can be completed this week, this is my "sprint" - I have to keep rolling out new areas, so I break down larger parts of the projects into small manageable parts. Usually this entails one larger area, and a handful of smaller ones than can be completed in an evening, with the larger segment being spread over the week.
- Tackle them
- Deliver (ie upload), usually on a Thursday evening.
Now I work alone, so it's not quite the same as the classic Scrum methodology but it's not that far off.
Currently for example I have a huge array of written content to cross-link and illustrate. When I say huge, it's going to be five or six hundred pages, easily the biggest new single area added in some time. I recently uploaded a new area for the UK - spread over several weeks, I kept delivering new pieces or versions until completion. That will be my approach with the Irish content.
Sadly because I work alone, I don't have the daily scrum meetings, it would be too strange....
Trackbacks
Trackback specific URI for this entry
No Trackbacks