sprints

See the forum [1], watch the sprints [2], look at GitHub [3] and watch their dev in Rust.

Microsoft Edge is at 63% and it will be updated in 6 week sprints like Chrome supposedly.

You’ll be responsible for the planning and execution of sprints, building feature functionality, and maintaining and scaling our existing application.

Essentially you are bringing the benefit of hackathons & sprints to internal projects, using the structure of a conference for framing.

I'm also pretty competitive, so things like sprints at the track and basketball help with the cardio side.

It is an ideal place for coding camps and sprints - rentals are cheap.

No sprints, no backlog, no retrospective, no well-defined stories, and no clue what our pace of development was.

I've used modafinil for personal 96 hour sprints, and while it works, I can't even describe the nightmares I had during the 18 hours I'd then sleep.

The advantage of sprints is that you're demoing progress on a regular basis.

I've been on a project where we had marketers join our sprints, and we're even assigned stories.

Many good development environments include technical debt as stories in their sprints.

I can't imagine the first sprints: First the infrastructure for A320 then iterate through to A380?

Yeah, especially when there are no clearly defined "sprints".

A few use-cases / benefits: * An agile team could use this as part of their retrospectives, and could track the data points across multiple sprints to see trends, as well as "scoring" the latest sprint.