Weekly Scrum readings follow up - CW48/2012

Background

This time you can follow my readings about agile metrics, the professional ladder (HR) and a nice input how to improve your way of doing code reviews. In the middle - find the relaxing moment ;-)

Readings Overview

• Agile Metrics (Pdf presentation by Danube technologies), Running Tested Features Metric (Blog post)
• I stumbled upon - stumble upon and started reading about 50 life secret tips and as it's the web ende in the fascinating world of alternative sleep methods and a cool speed reading software
  http://www.
  . ?
• Peer Code review: An Agile Process (Pdf overview by SmartBear)
• Just enjoy and relax for a short moment (click and see)
• Professional ladder (Blog post), 12 steps to better code (Blog post)
• 5 reasons your top employee isn't happy (Blog post)  

More detailed information

Agile metrics

Sources: Agile Metrics (Pdf presentation by Danube technologies) and Running Tested Features Metric (Blog post)

The Running Tested Features metric is described as a nice metric to foster agility and is not that easy to game. 

What is RTF about:

1. The desired software is broken down into named features (requirements, stories) which are part of what it means to deliver the desired system.
2. For each named feature, there are one or more automated acceptance tests which, when they work, will show that the feature in question is implemented.
3. The RTF metric shows, at every moment in the project, how many features are passing all their acceptance tests.

I think I'll give it a try - and update you later how it worked for me. Maybe you start in parallel and we collaborate by feedbacks and discussions?

The presentation about Agile Metrics gives a nice overview about various agile metrics, their usages and drawbacks (leading to wrong conclusions and possible gamings). Together with good examples it's a hands on introduction to agile metrics.

Stumble upon - that lead me to life secret tips, alternative sleep methods and speed reading

Sources: stumble upon, reading about 50 life secret tips, alternative sleep methods and cool speed reading software

Stumble upon is in my opinion a new fascinating platform that fills the gap between high quality posts and social networking. In addition to Facebook or Google+ it offers really cool articles that are suggested by your interest profile. Check it out and I promise you will stumble upon and stumble upon and finally ... stumble upon.

Mapped to Scrum and Agile - this platform enables new hub connections and generating new ideas (more details: Foster innovation by creating a learning and social networking environment for your teams).

Regarding the alternative sleep - I think I'll try the Everyman sleep schedule. What it brings? More time to read ;-)

I really enjoyed reading about 50 life secret tips, as it gives some input what to maybe consider in your teams too. Some of the suggestions you can use in your retrospectives, many are inspiring ... e.g. I started writing my daily dairy. 

Speed reading is a nice way to increase your knowledge acquiring productivity significantly. I ordered the mentioned software and really like the nice introduction workshop videos that already influenced the way I'm working now. I'm not yet finished with the training sessions, but at least from the measurements I'm already faster in reading and understanding texts. More on speeding reading maybe later...

Peer code review

Sources: Peer Code review: An Agile Process (Pdf overview by SmartBear)

"Statistics prove that peer code review is one of the most effective ways to improve software quality by reducing defects upstream. 

By aligning a peer code review approach with your specific goals and Agile sprints, code review becomes incredibly Agile and delivers many soft benefits that evolve from renewed focus on interaction and collaboration."

This document gives a good background why having code reviews in an agile way can increase your productivity. Starting with what makes a code review agile, it describes ways of doing reviews, best practices and suggests a combination of metrics for measuring and improving your review process.

e.g. Described best practices

• Limit the time dedicated for code review 
• Go slowly (do not review more than 200 to 500 lines of code per hour)
• Limit the amount of code reviewed (200 to 400 lines)
• Annotate the materials before the review starts (by looking at code using tools other than their standard editors)
• Keep Review checklists short

Professional ladder and a simple test for better code

Sources: Professional ladder (Blog post), 12 steps to better code (Blog post)

The Professional ladder describes an objective way for defining career levels (leading to salary levels). It's done by combining experience, scope and skills. Combined with the professional ladder, Joel Spolsky conducted a 12 step test to check your way of writing code. 

5 reasons your top employee isn't happy

Sources: 5 reasons your top employee isn't happy (Blog post)  

1. Inconsistent / Frequently Changing Priorities

2. Condoning Mediocrity

3. Round Peg / Square Hole Syndrome

4. Underutilization

5. Playing Favorites

For me the post contains some useful hints for a Scrum Master to check if this could apply to the team.