27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

the project. This achievement has three thresholds/medals<br />

defined to the percentual of acceptance: Bronze<br />

(50%); Silver (75%); and Gold (100%).<br />

2) Artifact Achievements:<br />

• Sprint Backlog Completion (SBC). SBC is a repetition<br />

achievement that accounts for the number of sprints<br />

where all the item in the Sprint Backlog were developed.<br />

The achievement has 3 levels: Level 1 (>= 1); Level 2<br />

(>= 3); and Level 3 (>= 10).<br />

• Sprint Review Acceptance (SRA). SRA is a team rate<br />

achievement that accounts for the number of accepted<br />

items by the PO in a review meeting compared to the<br />

total of items from the backlog of the current sprint. For<br />

this achievement three thresholds/medals were defined to<br />

the percentual of acceptance: Bronze (50%); Silver<br />

(75%); and Gold (100%).<br />

3) Cerimony Achievements:<br />

• Clockwork Developer (CD). CD is a rate individual<br />

achievement that accounts for the number of tasks a<br />

developer finished compared to the total number of tasks<br />

in an sprint. For this achievement three thresholds/medals<br />

were defined to the percentual of acceptance: Bronze<br />

(50%); Silver (75%); and Gold (100%).<br />

• Clockwork Team (CT): CT is a repetition team achievement<br />

that accounts for the number of tasks finished by the<br />

team in a Sprint, on the planned time (with difference up<br />

to 20%). The achievement has 3 levels: Level 1 (>= 1);<br />

Level 2 (>= 3); and Level 3 (>= 10). The Clockwork<br />

Developer and Clockwork Team achivements are classified<br />

as cerimony achievements because the success to<br />

accomplish a task on the planned time is associated to a<br />

well done planning.<br />

• Daily Scrum Developer Presence (DSDP). DSDP is an<br />

indivual rate achievement that accounts for the number<br />

of participations of each developer at standups during a<br />

Sprint compared to the total of days of each Sprint. For<br />

this achievement three thresholds/medals were defined to<br />

the percentual of acceptance: Bronze (50%); Silver<br />

(75%); and Gold (100%).<br />

• Daily Scrum Team Realization (DSTR). DSTR is a<br />

team rate achievement that accounts for the number of<br />

days that a daily scrum meeting was performed by the<br />

team compared to the total number of days of a Sprint.<br />

For this achievement three thresholds/medals were defined<br />

to the percentual of acceptance: Bronze (50%);<br />

Silver (75%); and Gold (100%).<br />

• Sprint Latency (SL). SL is a repetition achievement<br />

that accounts for the number of sprints started after a<br />

sprint end within a maximum time gap of 24 hours.<br />

The achievement has 3 levels: Level 1 (>= 1);Level<br />

2(>= 3); and Level 3 (>=10).<br />

B. Results and Analysis<br />

The evaluation performed has considered four achievements:<br />

one rate achievement for individual developers and<br />

three repetition team achievements.<br />

As mentioned before, we used historical data to compute the<br />

aforementioned achievements and award a selection of four<br />

project teams, comprising a total of 16 developers, during a<br />

time frame ofsevenmonths, which encompasses from nine<br />

to twelve Sprints from these four projects. The difference in<br />

the total amount of sprints for each project exists because<br />

each team can eventually work with different time boxes, also<br />

having time gaps among iterations.<br />

The result of the clockwork developer achievement award<br />

is shown in Table I. There is the indication of the number<br />

of medals that would be earned by each developer, according<br />

with his project. The developers could have earned up to ten<br />

gold medals in the considered period. From the analysis, we<br />

can observe that an individual developer would win earn up<br />

to seven medals. At least one medal will be earned for each<br />

developer.<br />

Clockwork Developer<br />

Project Developer Medals<br />

Project I Developer A<br />

Project I Developer B<br />

Project I Developer C<br />

Project I Developer D<br />

Project I Developer E<br />

Project II Developer F<br />

Project II Developer G<br />

Project III Developer H<br />

Project III Developer I<br />

Project III Developer J<br />

Project III Developer K<br />

Project IV Developer L<br />

Project IV Developer M<br />

Project IV Developer N<br />

Project IV Developer O<br />

Project IV Developer P<br />

Project IV Developer Q<br />

TABLE I<br />

INDIVIDUAL RESULTS FOR THE CLOCKWORK DEVELOPER ACHIEVEMENT,<br />

GROUPED BY PROJECT: TOTAL MEDALS EARNED BY EACH DEVELOPER<br />

DURING THE SPRINTS CONSIDERED IN THE PRELIMINARY EVALUATION.<br />

Table II shows the levels registered for each team considering<br />

the Clockwork Team achievement. All project teams<br />

reached at least the Level 1. This means that all teams<br />

completed at least one sprint on time. Projects II and III<br />

completed two sprints on the time among nine and twelve<br />

sprints respectively, but this fact did not assure a level update.<br />

Only Project I reached Level 2, since it has completed six<br />

sprints on time.<br />

Table III shows the levels registered for Sprint Backlog<br />

Completion achievement. Only Project IV did not reach the<br />

Level 2. The Project II team completed all the sprint backlog<br />

six times, from nine possible times. It is the best team in this<br />

criteria, however it did not reach the Level 3.<br />

Table IV shows the levels registered for Sprint Latency<br />

548

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!