Showing posts with label scrum. Show all posts
Showing posts with label scrum. Show all posts

Saturday, September 15, 2007

The Break Between Sprints

One element of agile development that is often forgotten in the heady drive to increase velocity is to truely take a break and recharge those creative juices. This struck me at a concert during the aptly titled song "White and Nerdy" by none other than Weird Al.

We all have to remember that you must play hard to work hard. Who better than Weird Al to let you laugh at him, the world, and most importantly yourself.

Thursday, August 23, 2007

Agile 2007 Conference Notes from a Newbie

What a week. I’ve never done booth duty before, and as a introverted product development type, it’s exhausting. I tried to flee to attend as many session as possible, mostly product management and Fit related sessions. So here goes with my notes from the conference:

Monday

Did some booth setup and attended a session by Naresh Jain of Thoughtworks and Micah Martin (yes, Uncle Bob’s son) on Acceptance Test Driven Development, where they described a lot of patterns and best practices in ATDD and using FitNesse. Some of the main ideas: write independent tests, don’t put everything in one big test, cleanup and teardown after your tests, avoid repeating by using includes, and don’t have too long of a feedback loop when using a build tool like Cruise Control – try out open source products like ProTest to get you feedback on your checkin within 5 minutes.

In the evening we checked out the ice-breaker in the ballroom and had a good chat with Rick Mugridge, the creator of Fit library. He was a walking booth with his ZiBreve shirt and hat – the shirt even had screenshots.

Tuesday

From my booth I could see a bit of the keynote by Susan Ershler. I spoke to her afterwards and got her book for my husband – she’s pretty inspiring. She and her husband were the first couple to climb the Seven Summits, including Everest. On her quest up Everest she had to try it a couple times, and go up and down to camps so the basic idea was sometimes to reach new heights you gotta do a bit of backtracking, and struggle long and hard.

Then I worked the booth. A fellow Canadian I met in the cafĂ© suggested I attend the session on Google’s Agile Adoption and I wish I had – I heard it was excellent.


Wednesday
I was up, bright and early, to check out Rick Mugridge and David Hussman speak about Executable project documents (basically about Fit). We spent some time writing up user stories and Fit tests. David was funny and it was well presented, but it was basically the same content as in the Fit book, “Fit for Developing Software.”

Then in the afternoon, I checked out the leadership symposium in the South Ballroom. Saw 2 good talks, one on Agile Memes (successful Agile patterns basically) by Steve Baker and Joseph Thomas from DTE Energy and one on Enterprise Agile at Yahoo by Gabrielle Benefield. Steve described how they got their big energy company using Agile by slowly phasing it in, trying on pilot teams, and getting teams to volunteer to try out scrum. They did their scrum meetings in the cafeteria and were open to people listening in, and made it fun by dubbing it “Big Pop Time” (someone started a trend of getting a huge pop and making scrum a fun break in the day.) Gabrielle described how she similarly piloted scrum at Yahoo and got mass appeal by giving out cute Agile t-shirts, hiring very outgoing Agile coaches, making it a defacto almost subversive process rather than mandated. She basically made scrum and Agile cool, and it spread around Yahoo.

Thursday

I went to Gabrielle Benefield and Michael Holzer’s session on User Centred Design for Agile projects. They described their unusual research methods for finding out what users, in their case teenagers, wanted out of products and creating user profiles to help understand their target market.In “Agile Ghettos or Thriving Communities”, Chris Avery and Michael England presented the idea that we should have Agile methodologies move beyond product development departments up to the executive level. There is a divide between these levels, and having a scrum of scrums and more collaborative work between executive could bring productivity gains. They described many case studies of this working at unique companies, including WL Gore (they make Gortex). And Friday we flew home. It was an exhausting week and I did a lot of demos of FITpro and got some feedback, but that will be the topic of another blog post. See you at Agile 2008 in Toronto!

Friday, July 20, 2007

On engineering practices in Scrum

The following couple of articles helped me to understand better the nature of the Scrum.

When is Scrum not Scrum? by Tobias Mayer and Differences Between Scrum and Extreme Programming by Mike Cohn

Both articles pay special attention to using engineering practices in Scrum. Both agree on importance of the practices and their value for the development process. More radical Tobias (he was expelled from the Scrum Alliance) thinks that they should be mandatory. Mike takes less categorical approach.

This is the bullet point list from "When Scrum is not scrum":

1. Product Owners are part of the team.
2. Two-week Sprints
3. Tasks are not measured in hours
4. Use of Taskboards rather than spreadsheets
5. Backlogs on the wall
6. Estimation Meetings
7. Insistence on Agile Engineering practices
8. The Scrum Master role is not always necessary

Here is an excerpt from Mike's article:

"I find true XP to be a small target off in the distance. If a team can aim at that and hit the bull’s eye, wonderful. If not, however, they are likely hacking (e.g., refactoring without any automated testing or TDD). Scrum is a big bull’s eye that on its own brings big improvements simply through the additional focus and the timeboxed iterations. That’s a good starting point for then adding the XP practices."


-Alex

Friday, July 6, 2007

Why We Scrum

I read an article today complaining that scrum was just another useless meeting and that the time would be put to better use speaking to the other developers about design issues one on one. I tend to disagree.
At a previous company, during our waterfall days, product managers tended throw requirements over the wall as they were busy. As a tester, I often found large discrepancies between my interpretation of the requirements and what the developer had coded into the product. On occasion I had to strong-arm developers into the product manager's office so we could come to a common understanding of a feature.
We had product development offices in Boston and Vancouver, so often the product manager, tester and developer were not co-located and had never met.
Scrum helped alot. When daily scrum meetings started up, we met our cross-department distributed team (face-to-face or over phone/video conference) and had a daily opportunity to discuss all the little questions and blockages that come up as you code and test. We came to a common understanding daily, and if we got astray from the feature vision the next day, it was still recoverable.
In conclusion, scrum breaks down the barrier of departments and lack of co-location, and gets a team communicating and collaborating. Cause many brains really are better than one.

Wednesday, February 28, 2007

What on Earth is a ScrumMaster?

This past week I completed the Certified ScrumMaster Course (CSM). Over drinks on Friday night, I mentioned this in passing to some friends. “What the heck is a ScrumMaster?” was the overwhelming reply. It’s a weird name, I’ll admit.

Well, before I took the ScrumMaster course, I figured that the ScrumMaster was an Agile Project Manager, who made sure the team followed Agile practices, facilitated the daily scrum and schedules sprints.

However, the course revealed another side to the ScrumMaster, that of a coach and shepherd. The ScrumMaster acts as a shepherd as they shield the team from external influences and over-commitment, and empower the team to make decisions, instead of making decisions for them. The ScrumMaster is the coach that cheers on the team, ensures they follow the rules (and enforces them through peer pressure), and teaches them how to self-organize and work with the Product Owner.

The ScrumMaster is really a facilitator, rather than a manager. In fact our ScrumMaster course instructor revealed that it would be best if the ScrumMaster were not a project manager or technical person; it was better if they were not, as they would rely more on the team to make decisions. It is best if the ScrumMaster is not a team member, as there would be a tension between oiling the machine and producing product. Any employee could be a ScrumMaster, if they have the right personality for the job; the kind of person that is approachable, trusted, people-oriented, and detail-oriented. I have read several articles implying that QA people make good ScrumMasters, as they have the right mindset (perhaps we are used to taking one for the team, being jammed at the end of the waterfall for so many years). ;)

Digg it! Bookmark this post to del.icio.us