IS HISTORY TEACHING US THAT AGILE IS DEAD?

@RROIC

JAVA DEVELOPER„AGILE CROATIA” BOARD MEMBERMANAGING SOFWARE DELIVERY @KING-ICTROCK CLIMBINGWRITING A BOOK ON AGILE

ROKO.ROIC@KING-ICT.HR

TECHNOLOGY

”THAT COOL THING WE USE FOR OUR PROJECTS”*

* EVERY DEVELOPER EVER

METHODOLOGY

”A SET OF METHODS, RULES, OR IDEAS THAT ARE IMPORTANT IN A SCIENCE OR ART : A PARTICULAR PROCEDURE OR SET OF PROCEDURES”*

* MERRIAM-WEBSTER DICTIONARY

BORIN

G

WHY METHODOLOGY?

NO SINGLE PERSON CAN DELIVER LARGE SOFTWARE PROJECTS IN REASONABLE TIME

THE SOLUTION

FORM A TEAM OF PEOPLE TO DO THE JOB.

WHICH BRINGS US TO FORMATION

THE HISTORY OF SOFTWARE DEVELOPMENT METHODS

UNTIL1960’S

MEANTIME IN TECHNOLOGY: COBOL, FORTRAN, PL/1, LISP, AGOLA, SMALLTALK, BASIC, A, B, LOGO

1970’S

Software development should be done incrementally,in stages with continuous user participation and replanning and with design-to-cost programmingwithin each stage.

MEANTIME IN TECHNOLOGY: C, PASCAL, MODULA, AWK, ADA, MS BASIC

1980’S

THE WATERFALL ACCIDENT

MEANTIME IN TECHNOLOGY: OBJECTIVE C, C++, SELF, EIFFEL, PERL, SML

1990’S- NOW

FIRST OF ALL, MONEY

CRYSTAL

1992.

1994.

SCRUM

1995.

RUP

1996.

XP

1999.

REFACTORING, CI, CD

1993.-…

AGILE, 2001.

LEAN SW DEV

2003.

KANBAN

2007.

YOU GET THE PICTURE (PUN INTENDED)

MEANTIME IN TECHNOLOGY: HASKELL, JAVA, PYTHON, RUBY, JAVASCRIPT, C#, VB, DELPHI, SCALA, …

WHAT DOES THE FUTURE BRING FOR METHODOLOGY?

IT BRINGS CERTAIN AND FAST CHANGE.

CHANGE IS A JOURNEY, IT IS NOT SOMETHING THAT TAKES PLACE AND FINISHES

METHODS ARE AT THE MATURITY LEVEL OF 1970S DEVELOPMENT LANGUAGES

THERE IS SOME PROOF WHICH METHOD IS BETTER

BASED ON THE „WATERFALL ACCIDENT”, CAN WE ASSUME THAT SCRUM IS AN ACCIDENT?

1950 - PDCA1960 – TDD @MERCURY, TPS1970 – TOM GILB, FSD @ IBM1980 – BOOK BY GILB1992 – CRYSTAL…2001 – AGILE2007 - LEAN

30 YEAR GAP!

WE CAN SAFELY ASSUME THAT THE BETTER METHOD IS COMING ALREADY HERE

UNFORTUNATELY – WE STILL DO NOT KNOW ITS NAME

Q&AROKO.ROIC@KING-ICT.HR@RROIC