agile42

Lamentations of flaccid Scrum and a case for SINO

I've been updating myself on the activites in the Prince2 camp to update this project management framework. One thing that ...

On
31 March 2009
In
Scrum Sense

I've been updating myself on the activites in the Prince2 camp to update this project management framework. One thing that stuck is the lamentations about the large number of PINO projects. PINO is an acronym (actually an initialism) for Prince In Name Only. In the Scrum world this has commonly been called ScrumButt, drawn from "we're doing Scrum, but..." as well as the frequent desire to kick such teams in the butt!

Martin Fowler, one of Agile Manifesto signatories has blogged recently on "flaccid Scrum" (http://www.martinfowler.com/bliki/FlaccidScrum.html). FWIW, I agree with him.

We ...

Metrics & Myths

At the Scrum Gathering in Orlando last week Pete Behrens facilitated an Open Space session on "Metrics and Myths". We ...

On
27 March 2009
In
Scrum Sense

At the Scrum Gathering in Orlando last week Pete Behrens facilitated an Open Space session on "Metrics and Myths". We considered four categories of measurements: productivity, quality, predictability and value. In each we each contributed measurements that are either "metrics" or "myths". We stuck them up on a wall as you can see in the photos. In this first post I'm simply showing the pictures I took of the session. In subsequent posts, I aim to construct some reasoned arguments for a few Agile metrics Mike and I consider valuable to any organisation transitioning to Scrum.









Metrics & Myths

Scrum is a Change Management process!

Right now I'm sitting at the back of the class while my good friend André is conducting an introduction workshop ...

On
25 March 2009
In
Scrum Sense

Right now I'm sitting at the back of the class while my good friend André is conducting an introduction workshop on ITSM (IT Service Management) using the ITIL framework at a major retailer.

He tells a story to illustrate the difference between incident management and problem management. The latter requires a root cause analysis. The aha! moment for me is when he says that root cause analysis is the start of a CM (Change Management) process.

I realise that Scrum is an ongoing change management process. In every daily Scrum meeting, Sprint Review and Sprint Retrospective the team (and ...

Scrum and the Space Shuttle

I was fortunate to attend the Scrum gathering last week. It was held at the impressive Gaylord Palms resort in ...

On
25 March 2009
In
Scrum Sense

I was fortunate to attend the Scrum gathering last week. It was held at the impressive Gaylord Palms resort in Kissimmee, Orlando. I arrived early and spent Sunday visiting Disney's nearby Epcot theme park.

Space Shuttle Discovery launch 2009.03.15 19:45

Planet Earth at Epcot

Our evening cocktail party, hosted by the PMI, was interrupted to observe the launch of the space shuttle Discovery at Kennedy Space Centre, some 50 km East of Orlando. Just before the 7:43 pm launch time we gathered on an East-facing balcony to watch. This was to be the last night-time launch of the shuttle as we know it. We weren't disappointed.

Planning Poker Cards

Use these simple Planning Poker decks to break down complex software engineering problems into manageable chunks, and estimate fast and precise. The Planning Poker Card Decks come together with the Business Value Game.

On
18 March 2009
In
General
Tags
agile, estimation, planning poker, planning poker cards, scrum

Hi there,

to estimate tasks we use in our projects the planning poker cards. It makes fun and gives clear rules to the team to evaluate the effort of a task.

You can order them on our Planning Poker Page

Have fun Marion

What is Planning Poker?

Planning poker is a variation of the Wideband Delphi method. It is simple, makes fun and results in reliable estimates.

Planning poker is mostly used to estimate the effort or the relative size of tasks in software development. The members of the project team come together and estimate each item in a few ...

How we organize the Scrumtisch

Some information on what you can expect when visiting the Berlin Scrumtisch.

On
9 March 2009
In
Scrumtisch Berlin
  1. Finding the topics
    Of course we appreciate proposals upfront for the upcoming Scrumtisch, but mostly people are busy and therefore we collect wishes and questions at the beginning of the event. We write these questions on the "wall" and after we prioritize them. We can make use of electrostatic whiteboard, and a projector, so if you want to prepare something, you are really welcome, just post your idea into the Scrumtisch website

  2. Timeboxed discussion
    The 2 highest prioritized "Topics" will be discussed. The others are ending up in a backlog for the next Scrumtisch. We focus on each of the ...

Scrumtisch Berlin, April

The April Scrumtisch in Berlin: 22nd April 2009 Thoralf from NSN will talk about: Agile Creation of Multi-Product Solutions. We are looking forward to this interesting speech.

On
9 March 2009
In
Scrumtisch Berlin
Tags
agile, scrum berlin, scrumtisch

Hi all together,

last time the invitation to the next Scrumtisch came really late. Therefore here the invitation for the next one a bit more in advance ;-)

The next Scrumtisch in Berlin takes place at:

Day: Wednesday, 22nd April
Time: 18:00 Uhr
Place: DiVino Restaurant, Grünberger Str. 69, Friedrichshain

Topic: Thoralf, will present his speech from the Orlando ScrumGathering

Agile Creation of Multi-Product Solutions

  • Motivation for Network Solutions and their Agility
  • Scaling Single Product Creation
  • Product Solutions using Scrum
  • Customizing Projects
  • Outlook

Please let me know if you are coming to be able to organise the space ;-)

Marion

Scrumtisch Berlin, März 2009

Der nächste Scrumtisch in Berlin findet am 03.02.2009 statt.

On
22 February 2009
In
Scrumtisch Berlin
Tags
agile, berlin, scrum, scrumtisch

Hallo Leute,

es ist wieder soweit. Der nächste Scrumtisch in Berlin findet am Dienstag den 3. März statt. Den Ort kennt Ihr ja und los geht's um 18:00 Uhr.

Bitte schickt mir kurz eine Mail, wenn Ihr teilnehmen wollt.

Bis dann Marion

Keep It Lean And Agile ("KILAA")

PHP Magazin Print-Editon: 6.2008: Agile Development mit Scrum Keep It Lean And Agile ("KILAA") More and more companies who until recently developed using more conservative methods such as Waterfall or RUP software, are now switching to lean and agile methods. Based on best practices agile processes offer so-called process frameworks, which can be customized individually, according to the respective needs of teams and projects. Sounds good so far but let’s examine the pros and cons, areas of usage, implementation, long-term application and, lastly, the differences to other methods such as CMMI. And when it’s all said and done: the final answer.

On
10 December 2008
In
Press

PHP Magazin Print-Edition: 6.2008:

Agile Development mit Scrum

Keep It Lean And Agile ("KILAA")

More and more companies who until recently developed using more conservative methods such as Waterfall or RUP software, are now switching to lean and agile methods. Based on best practices agile processes offer so-called process frameworks, which can be customized individually, according to the respective needs of teams and projects. Sounds good so far but let’s examine the pros and cons, areas of usage, implementation, long-term application and, lastly, the differences to other methods such as CMMI. And when it’s all said and ...

Keep It Lean And Agile ("KILAA")

PHP Magazin Print-Ausgabe: 6.2008: Agile Development mit Scrum Keep It Lean And Agile ("KILAA") Mehr und mehr Unternehmen, die bisher mit konservativen Methoden, wie beispielsweise Wasserfall oder RUP Software entwickelt haben, steigen um auf “lean” und agile Praktiken. Basierend auf Best Practices bieten agile Vorgehensweisen so genannte Process Frameworks, die individuell auf die jeweiligen Teams und Projekte abgestimmt werden. Klingt gut - aber stellen wir auch kritische Fragen nach den Vor- und Nachteilen, den Einsatzgebieten, der Umsetzung, der langfristigen Anwendung und Abgrenzungen zu Vorgehensmodellen wie z. B. CMMI, bevor wir ein abschließendes Urteil bilden.

On
10 December 2008
In
Press

PHP Magazin Print-Ausgabe: 6.2008:

Agile Development mit Scrum

Softwareentwicklung - Ein historischer Ausblick

Lang lang ist’s her, dass die erste Software entwickelt wurde und fast ebenso lange, dass das erste Projekt NICHT in Zeit und Budget (… Das kenne ich doch irgendwoher...) abgeschlossen wurde. Vorgehensmodelle wie das Wasserfallmodell oder RUP wurden mit der Hoffnung geboren, man könne Ingenieurpraktiken auch in der Softwareentwicklung anwenden. Diese Vorgehensweisen sind strukturiert, dokumentenbasiert und versuchen, die Software Entwicklungsprozesse zu vereinheitlichen. Wie bei industriellen Produkten, wird hier viel Zeit und Energie auf die Planung im Vorfeld gelegt. Anforderungen werden niedergeschrieben, langfristige Planungen sollen Sicherheit geben und ...

Latest entries

Scrumtisch October 2017

Scrumtisch Berlin October 2017

 

Scrumtisch Berlin: August 22nd, 2017

August 2017 meeting of the Berlin Scrum User Group, facilitated by agile42 coaches Noel Viehmeyer and ...

 

Certified Agile Leadership comes to Vancouver

First part of the Scrum Alliance Certified Agile Leadership (CAL) program will be available in Vancouver ...

 

Survival Tricks for Remote Developers

Video and slides of the talk presented by Alessio Bragadini at PyCon 8 conference in Florence, ...

 

Sponsoring Agile Africa

agile42 sponsors Agile Africa 2017 in Johannesburg, 21-22 August