ALM | Ingénierie Logicielle

Here's an overview and comparison between two popular large-scale agile frameworks: Scaled Agile Framework (SAFe) and Disciplined Agile Delivery ...

Inherent software complexity is not the only important factor; so are team size, location and distribution, regulatory constraints, and requirements management. With no two teams working exactly alike, no single formula or methodology can address all needs.

Scott W. Ambler, 09/09/2014

In one of my previous post, I mentioned about how we raised agile awareness with various games (self-organised team, lean “flow”, etc..)

Imagine my surprise when Agile 2.0 was “announced” at the recent EclipseCon 2013 in Boston. Here I am thinking the simple tenets so clearly outlined in the The Agile Manifesto of 2001 have yet to be fulfilled by most software organizations more than a decade later.

Inspirée d’outils de coaching classique (type roue de la vie), cette roue du Management Agile m’aide dans mon travail d’accompagnement des Managers impliqués dans des projets de transformation Agile. Merci à@bangalaurent de m’avoir aidé à la formaliser!

There is a significant change in how software is developed over the last decade. Agile had been the buzzword over the last decade and probably is most significant of changes in software development to date.

It is important to stabilize feature richness with simplicity to a team’s acceptance of agile life cycle management. A comparative analysis based on the feature is an important part of a company’s evolution; however it is also essential to consider the main business aspects that will impact your long-run success.

This is a book that sums up any large organisation with a software delivery function. It certainly matches the experiences in my last company but also matches the many case studies I have heard from my colleagues over the years.

It starts by defining enterprise software delivery, noting it uses the word delivery and not development. This is on purpose as software development is only useful when in the hands of the end-user.

In the 1990s and early 2000s a number of different lightweight "agile" development methods sprung up.

Today a few shops use Extreme Programming, including most notably ThoughtWorks and Industrial Logic. But if you ask around, especially in enterprise shops, almost everybody who is “doing Agile” today is following Scrum or something based on Scrum.

Comment mesurer objectivement l'efficacité des méthodes agiles sur un projet ? Est-ce que tous les projets sont agilisables ? Répondons à ces questions !

Robin Béraud-sudreau, 07/04/2014

This article describes the relationship between architecture and process of software development and how architecture can responds to a set of needs, such as functional requirements, operational characteristics, and developer habitability.

It’s been a funny transition the past few years as agile has gone more and more mainstream. You used to have to start every talk with an explanation of the Agile Manifesto… you don’t have to do that anymore, people generally get it. You used to have to start every talk with an explanation of why waterfall has failed… you don’t have to do that anymore, people for the most part realize waterfall has failed.

Selon un rapport publié cette semaine par l'éditeur VersionOne, les projets de développement « agile » aboutissent le plus souvent, mais quand ils échouent, c'est généralement d'abord à cause d'une dotation insuffisante en personnel et ensuite pour des questions de culture des équipes.

The wait is over for the next generation of ALM, as new Agile ALM tools and techniques provide a path to greater productivity. To many in the IT industry, the introduction of application lifecycle management (ALM) as a central discipline in software development ten years ago was seen as nothing short of revolutionary. But every revolution must itself confront change, in this case overcoming challenges with legacy ALM products that proved to be too monolithic, inflexible or costly to manage.