Scrum Software Development Process

Introduction

In this article I give an overview of the Scrum Software Development Process. This methodology was first described by Takeuchi and Ikujiro in their 1986 book “The New New Product Development Game“, and was initially meant to manage any kind of product development project. This methodology, for example, has been used in “real” product development projects by companies such as Fuji-Xerox, Canon, Honda, NEC, Epson, Brother, 3M, Xerox and Hewlett-Packard (Schwaber). In the nineties it was adapted for software development projects. Continue reading

What will the Software Architecture discipline look like in 10 years’ time?

Introduction

This is a tricky question; after all, Bill Gates himself published a book in 1995, “The Road Ahead”, where he only slightly talks about the World Wide Web:

“The Road Ahead” appeared in December 1995, just as Gates was unveiling Microsoft’s master plan to “embrace and extend” the Internet. Yet the book’s first edition, with its clunky accompanying CD-ROM, mentioned the Web a mere seven times in nearly 300 pages. Though later editions tried to correct this gaffe, “The Road Ahead” remains a landmark of bad techno-punditry — and a time-capsule illustration of just how easily captains of industry can miss a tidal wave that’s about to engulf them. (Salon.com, 2000)

Thus, trying to extrapolate our own craftsmanship up to 2016 is inherently tricky, but a nice thought experiment after all. Continue reading

Starting a new adventure

So here we go again.

Last week I started my new job, as Software Solutions Consultant for Getronics, in Lonay, near Lausanne (where I live), Switzerland. Yeah, the commune of Lonay has an awful website. Anyway. The good news is Getronics, actually.

My job, as usual, will be one with multiple faces. I will be in charge of technical consulting for the pre-sales and development teams, and also architecture and training. As you can see, nothing to make you feel bored. But in any case, a big improvement over my previous employer, mostly in terms of growing possibilities, infrastructure, diversity of clients, and learning opportunities. Continue reading

SLOCS and other statistics

The Reuters’ project I’ve previously written about is finally coming to an end, at least version 1.0. It is now “feature complete” and tomorrow it will be deployed in their own servers. That’s a nice milestone!

Then I asked myself, how many lines of code have I written during this month? How many did I write per day in average? This is an unique opportunity to know, since I have been responsible for this little project from beginning to end, from analysis to design and implementation and testing, through the installation in their own infrastructure. Continue reading

Metodos de Desarrollo de Software: Desafio Pendiente de la Estandarizacion

Encontre este articulo en español, y me parecio menester hacerle una referencia: me parecio excelentemente bien redactado y claro, y recomiendo su lectura!

http://omega.fdo-may.ubiobio.cl/th/v/v12/2.pdf

Por Ricardo A. Gacitúa Bustos, Depto. Sistemas de Información, Facultad de Ciencias Empresariales, Universidad del Bío-Bío, Avda. Collao 1202, Concepción, Chile, e-mail: rgacitua@ubiobio.cl

Este artículo describe la evolución de los métodos de desarrollo de software. El foco está centrado en el desacuerdo en cómo debe crearse el software. El tema es como se considera el desarrollo de software: como un proceso de ingeniería o un proceso centrado en las personas. Se presenta el lenguaje de modelamiento unificado (UML) como una notación estándar del desarrollo de software. Actualmente es considerado como base para una metodología monumental (que incluye muchas reglas y prácticas) – RUP. Se menciona la reacción a las metodologías monumentales: los métodos ágiles. La cual es característica de un estado inmaduro del desarrollo de software como una disciplina. No solo hay desacuerdo en terminologías, enfoques y detalles de diferentes métodos, sino incluso en un esquema de clasificación común. La siguiente estructura está basada en la evolución de los principales conceptos y las distinciones claves que reflejan los cambios de paradigmas en la filosofía de métodos.

(copia local por si el link remoto no funciona)