RubyConfUA - Measuring Agile Process with Ruby, Hubert Łępicki

8/7/2019 RubyConfUA - Measuring Agile Process with Ruby, Hubert picki

1/51

Me asuring Agile ProcessWith Ruby

RubyConf Ukraine 2010

Hubert [email protected]
mailto:[email protected]:[email protected]


2/51

Me


3/51

Hubert picki


4/51

[email protected]

[email protected]

github.com/hubertlepicki

twitter.com/hubertlepicki

hubertlepicki.com


5/51


6/51


7/51

http://amberbit.com


8/51


9/51


10/51

Agile


11/51

Hot topic


12/51


13/51

http://agilemanifesto.org


14/51

Individuals and interactions over processes and tools

Working software over comprehensivedocumentation

Customer collaboration over contract

negotiation

Responding to change over following aplan


15/51

no process and tools?

no documentation?

no contract negotiation?

no plan?


16/51

WRONG


17/51

There are contractssimple

flexible

service over product


18/51

it "should have documentatio

it "should be readable"

it "can be in form of tests"

it "can be in form of code"


19/51

there must be a plan


20/51

The processwell defined by methodology

eXtreme Programming

Scrum

Kanban

Crystal


21/51

What do they have incommon?

iterations

incremental development

defined roles in project


22/51

What are the differences?eXtreme Programming: engineering

practices

Scrum: project management

Kanban: fast delivery of features


23/51

Why do we (Rubyprogrammers) use Agile

methodologies?they fit object oriented programming

they have simple rules

they can reduce/control chaos


24/51

Despite trying toimplement agile

methodologies, sometimesthings go bad.

how bad?


25/51

I used to work on aproject we were going to

finish in October 2007we finished in October

2008

that bad

(that was BEFORE we started AmberBit;))


26/51

What is to blame?bad programmers

bad management

wrong implementation of agilemethodologies(http://www.halfarsedagilemanifesto.org/)


27/51

If a project fails, you want to know whatwent wrong

During development, you want to knowif things are likely to go wrong


28/51

You need to measure theprocess

yeah, but how?


29/51

Let's thing what can gowrong during the project

poor implementation of agilemethodologies

communication problems

software quality degrades

project doesn't meet budget, scope or time


30/51

and many more


31/51

What to measure - a fewexamples

project size

team velocity

project progress

value of one story point in time


32/51

number of passing/failing tests

code complexity

code coverage

test to code ratio


33/51

ToolsYour issue tracker

Ruby

CI builds


34/51

Project sizerake stats


35/51

+----------------------+-------+-----| Name | Lines | LO+----------------------+-------+-----| Controllers | 519 | 40| Helpers | 43 | 3| Models | 658 | 49| Libraries | 119 | 8

| Model specs | 854 | 71| View specs | 5 || Helper specs | 18 | 1| Acceptance specs | 371 | 29+----------------------+-------+-----| Total | 2587 | 205+----------------------+-------+-----

Code LOC: 1021 Test LOC: 1036


36/51

# Quick and dirty way to get

# in source code of your apDir.glob("app/**/*.rb").col`cat #{f} | wc -l`.to_i

end.sum


37/51

# Better, get only number o

Dir.glob("app/**/*.rb").colFile.readlines(f).select{|l| !(l =~ /^\s*($|#)/)

}.sizeend.sum


38/51

Test resultsWhen using RSpec, write your own

formatter

or hook into BaseFormatter:


39/51

Monkeypatching RSpclass Spec::Core::Formatters::

alias_method :old_dump_summ:dump_summary

def dump_summary(*args)old_dump_summary(*args)

Faraday.get("http://mydom"passed=#{args"&failed=#{ar

endend


40/51

Code complexitywhy bother?

it can be a measure of technical debt

debt removed earlier is easier to manage


41/51

Static code analysis withRuby

Flog - http://ruby.sadi.st/Flog.html

Saikuro - http://saikuro.rubyforge.org/

^^ these are 1.8-only ^^

metric_abc - http://github.com/hubertlepicki/metric_abc


42/51

metric_abc in action$ metric_abc user.rbuser.rb > User > update_flagg

user.rb > User > initialize: 1user.rb > User > vote_on: 13user.rb > User > generate_reauser.rb > User > thumbnail_uruser.rb > User > visit_ids: 8user.rb > User > already_voteuser.rb > User > suggested_lo...


43/51

ok, now what?calculate metrics

store metrics in database

visualize metric changes over time


44/51

examples


45/51


46/51


47/51


48/51


49/51

how to plot?Gnuplot.open do |gp|

Gnuplot::Plot.new( gp ) do |

x = ProjectSize.all.colley = ProjectSize.all.colleplot.title "Project Size"plot.ylabel "LOCs"plot.xlabel "days"

plot.data


50/51

Final notesdo not trust metrics, treat them as

inteligence reports

analyse periodically

analyse failed projects

take actios to fix processes in your

teams


51/51

Thank you!

Documents

RubyConfUA - Measuring Agile Process with Ruby, Hubert Łępicki