PUBLIC   marks

PUBLIC MARKS with tag methodology

Sponsorised links

This year

Evidence Based Scheduling - Joel on Software

by greut (via)

Using Evidence-Based Scheduling is pretty easy: it will take you a day or two at the beginning of every iteration to produce detailed estimates, and it’ll take a few seconds every day to record when you start working on a new task on a timesheet. The benefits, though, are huge: realistic schedules.

Realistic schedules are the key to creating good software. It forces you to do the best features first and allows you to make the right decisions about what to build. Which makes your product better, your boss happier, delights your customers, and—best of all—lets you go home at five o’clock.

A more general approach that the SCRUM one I got so far.

Bootstrapping a decentralized Twitter (Scripting News)

by benoit

I always work in bootstrapping mode, addressing the first big issue, solving the problem, then advancing to the next one. It's why so many of the ideas I've worked on have become popular modes of communication. Big-bang approaches always fail. I've spent decades arguing with people who want to reinvent the world in one stroke. They always try anyway and always fail. Bootstrapping is the only way that works.

CMMI imp

by holyver
J'ai dit ici ce que j'ai compris de CMMI[1] afin de faire ressortir ses apports comme ses limites. Je serai reconnaissant à ceux qui, comme l'ont fait MM. Didier Dulac et Jacques Printz, voudront bien m'indiquer les corrections et compléments qui leur semblent nécessaires pour améliorer cette analyse, qui s'appuie sur une lecture critique de la documentation sur CMMI. Le mot critique doit être pris ici non au sens de dénigrement qu'on lui attribue dans le langage courant, mais au sens technique et précis de délimitation : il s'agit de délimiter ce que CMMI apporte, ce qui implique d'indiquer ce qu'il n'apporte pas.

Sponsorised links

2007

2006

Home - OpenBRR

by mbertier
Business Readiness Rating™ (BRR) is being proposed as a new standard model for rating open source software.

Control Chaos

by mbertier & 1 other
Scrum is an iterative, incremental process for developing any product or managing any work. It produces a potentially shippable set of functionality at the end of every iteration. It's attributes are:

ハイパー マンダラ日記

by phgod
甚麼？原來「晨間日記」就是早上寫的曼陀羅！

2005

PUBLIC TAGS related to tag methodology

no tag

Sponsorised links