#informationradiator

We are excited to unveil the Vabro Velocity Report, a comprehensive analysis of our Scrum team's performance over recent sprints. This report is a vital tool for understanding our team's capacity and efficiency, helping us continuously improve our workflow.

Key Insights from the Velocity Report:

Velocity Definition: Velocity measures the amount of work our Scrum team completes per sprint, expressed in story points or tasks. It’s a key indicator of our productivity and consistency.

Velocity Chart: Our report includes a detailed chart showing velocity trends across multiple sprints. This visual representation helps us track our progress and spot patterns over time.

Average Velocity: The report highlights our average velocity, providing a benchmark for future sprints. Observing this trend helps us set realistic goals and expectations.

Velocity Variance: We also analyze significant changes in velocity between sprints, identifying factors that influenced these variations. This helps us understand what works well and what needs adjustment.

Forecasting and Planning: Velocity data is crucial for forecasting and planning. By knowing our team's capacity, we can make informed decisions about future projects and sprint planning.

Recommendations: Based on our analysis, we offer recommendations to enhance our velocity. These suggestions aim to optimize our processes and boost overall efficiency.

The Vabro Velocity Report is not just a retrospective look at our past performance but a forward-looking tool that drives our continuous improvement.

Are you interested in learning more about Vabro, Scrum, and agile methodologies?

There are two types of technical debt:

Technical debt that you introduce on purpose: because of deadlines

Technical debt that you are not aware of: little known technology, being a lesser experienced developer in a new language, 

If you come across Technical Debt, make sure to write that down somewhere. I recommend Tobias Mayer's approach on the task board. Although I have seen people using

//TODO: Implement proper age calculation

as well, highly visible Information Radiators are winners!

This is a litte project I started a while back but only finished/cleaned up recently. It's a simple information radiator that shows you what a Last.fm user is listening to right now.

It was designed to let one (or many people) know what's playing at a glance. I've been using it while listening to Last.fm radio while getting ready for work, shared office playback (it works really well here) and even on top of Spotify playlists at parties. You can stalk along to someone else's listening too, for the curious.

Dev/ops have made heavy use of radiators/glanceables for a while (that's a whole 'nothing post), but it's nice to see more social and experimental uses being applied. With "second screens" getting more popular I'm excited to see what else will get made soon.

Try the hosted demo version or fork the project on Github.

Responsiveness

It's not strictly a responsive-design (no media queries in sight) but it does work really well across multiple devices. Only needing some font size adjustments on larger screens. Matthew Sheret has been running this on an old iPod touch sat on his desk for a few weeks, quite happily.

How it works

There's no server-side requirement, everything is HTML/CSS/JS, no PHP or Python dependency, which means it's super easy to use locally. You can clone it from Github and use it immediately, no configuration. It includes a tiny Last.fm API client written in Javascript

Now-playing is part Last.fm scrobbling API, supported by most clients it's sent at the begining of a track rather than at the end (like scrobbling). Becuase there's no realtime API i'm polling on a with a tiny Javascript API client. By default it polls on a 5 second interval, which feels pretty snappy and sit well within the TOS (~1 req/sec max).