agilesWissen

Karl Scotland published a readable article about usage of “Kanban System” in software development:

…
The goal of a Kanban system is to minimise inventory, or Work in Process, and maximise throughput of value in the system.

Rather than Sprints, with their Sprint Planning meetings, we have moved to a weekly cycle in which we simply refreshed a buffer, or queue, of the immediate priorities to work. The items in this queue are Minimal Marketable Features (MMFs) – the smallest things which can deliver value on their own.
…
Rather, Lean thinking, and Kanban Systems suggest doing less up-front planning, and valuing focussed teamwork over process in order to deliver value quickly.

by Karl Scotland

1. Ineffective use of the retrospective
2. Inability to get everyone in the planning meetings
3. Failure to pay attention to the infrastructure required
4. Bad ScrumMasters
5. Product Owner is Consistently Unavailable or There are Too Many Owners Who Disagree
6. Reverting to Form
7. Obtaining Only “Checkbook Commitments” from Executive Management
8. Teams Lacking Authority and Decision-Making Ability
9. Not Having an Onsite Evangelist for Remote Locations
10. A Culture that Does Not Support Learning
11. Denial is Embraced Instead of the Brutal Truth

by Jean Tabaka

(big readable version) by energizedwork.com

.. Avoiding Pitfalls in an Iterative Model (by Leisa Reichelt)

slides via slideshare.net

There is a commonly held belief that Agile Methods and User Centred Design do not play nicely together. On the contrary, Agile and UCD have much to offer each other. Each can learn and benefit from the other, and work together as a robust design and development methodology.

Including an introduction to the principles and practices of Agile Methodologies, this presentation explores the opportunities for UCD in an Agile environment, how designers can shape Agile to better support their work, and what designers can learn from Agile methods.

Leisa Reichelt at Web 2.0 Expo Berlin from Johannes Kleske on Vimeo.

Die Web 2.0 Expo in Berlin vom 5.-8.11.2007 kommt, wenn man sich durchs Web klickt, nicht gerade gut weg. Viele beschweren sich über das schlechte Essen, die schlechte Wahl des Veranstaltungsortes, gestörtes WLAN usw.

Ok, wenn man die Konferenz besucht hat, um dort gut zu essen, war man dort in der Tat richtig falsch. Und es hätte den Organisatoren sicher auch nicht geschadet sich den Ort des Geschehens (Berliner Messegelände) vorher einmal genau anzuschauen. Allerdings zählt bei einer Konferenz letztendlich der Inhalt und der war, meiner Meinung nach, gut aufgestellt, um zu erfahren wie die Web 2.0 Community im allgemeinen tickt, welche Probleme und Herausforderungen es gibt und was die neuen Trends sind. Ich für meinen Teil konnte in den 4 Tagen folgende Highlights ausmachen:

Highlights

• Scalable Web Architectures, Common Patterns & Approaches (by Cal Henderson, flickr.com)
• Performance and reliability, how to run large web apps (by Artur Bergman, wikia.com)
• Web App Security, Keeping your application safe (by Joe Walker)
• How to make AJAX work for you (by Simon Willison)
• Better Typography (by Mark Boulton)
• Microformats the nanotechnology of the semantic web (by Jeremy Keith)
• The Beauty in Standards and Accessiblity (by Jeremy Keith)
• Designing for a Web of Data (by Tom Coates, Yahoo)
• Agile Development, Agile Design Avoiding Pitfalls in an Iterative Model (by Leisa Reichelt)
• Photosynth (by Blaise Aguera y Arcas, Microsoft Live Labs)
• Delivering Rich Experiences (by Jesse James Garrett, Adaptive Path)
• The Starfish and the Spider (by Rod Beckstrom)
• The Future of Firefox (by Tristan Nitot, Mozilla Europe)
• Enterprise 2.0, Wikinomics (by Don Tapscott)
• Creating Passionate Users (by Kathy Sierra)

Links

• Golem: Web 2.0 Expo in Berlin – “The Site is not your Product”
• Heise: “Web 2.0 ist ein Schlachtfeld”
• der Standard: Namensgeber O’Reilly sieht Ende des Web 2.0-Hypes erreicht
• So sieht Catering 1.0 aus..
• Web 2.0 Expo slides via Slideshare

Heute ist der 9. November und wie jeder weiß ist dies in Deutschland ein denkwürdiger Tag und das nicht nur in den Jahren 1848, 1918, 1923, 1938 und 1989 sondern auch 2007, denn heute hat der Bundestag das Gesetz zur Vorratsdatenspeicherung und TK-Überwachung verabschiedet und somit einen weiteren Grundstein für das Stasi 2.0 Projekt gelegt.

Links

• Arbeitskreis Vorratsdatenspeicherung
• Wikipedia Artikel zum Thema Vorratsdatenspeicherung
• Telepolis: Stasi 2.0

Wer sich diese Frage stellt, sollte sich die Studie vom britische Social Issues Research Centre (SIRC) ansehen:

Life online: The Web in 2020 – A study by the Social Issues Research Centre on behalf of Rackspace Managed Hosting