agilesWissen

see http://www.panic.com/blog/2010/03/the-panic-status-board/

If you search for a backlog tool, take a look on http://www.userstories.com/products.

For example, a simple and good backlog tool is eXPlainPMT

.

Here are my slides about Robert C. Martins great book “Clean Code: A Handbook of Agile Software Craftsmanship“:

This refers to a story Lopp told earlier in the session, in which he described the process of a senior manager outlining what they wanted from any new application: “I want WYSIWYG… I want it to support major browsers… I want it to reflect the spirit of the company.” Or, as Lopp put it: “I want a pony!” He added: “Who doesn’t? A pony is gorgeous!” The problem, he said, is that these people are describing what they think they want. And even if they’re misguided, they, as the ones signing the checks, really cannot be ignored.

Apple’s design process

Google Tech Talks
October, 30 2008

Clean Code Talks – Unit Testing

Speaker: Misko Hevery

Golem führte ein wirklich sehenswertes Interview mit Aza Raskin zum Thema Humanes Interface-Design und Firefox:

Links:

• Golem: Wie das neue User-Interface für Firefox entsteht
• Book: The Humane Interface. New Directions for Designing Interactive Systems. by Jef Raskin

• Web 2.0 Expo: Collaboration Techniques that Really Work – Productivity, Creativity and Consensus by Leisa Reichelt

Google Tech Talks
October 8, 2008

ABSTRACT

Ever notice that you seem to spend 80% of your time on 20% of your tasks? Or that 80% of the decisions in a meeting seem to occur in 20% of the meeting time? Welcome to the world of the 80:20 rule. When we design, build and test software, we have to determine where to start and what we should do next. The 80:20 rule helps provide an answer to these questions, while helping to increase our productivity and effectiveness. As well as being an agile principle, it’s a common thread in other disciplines, and there’s a special variation that applies to software defects. We’ll explore the different ways testers and developers are using the 80:20 rule. This rule could be a secret ingredient to help you build software smarter!

Speaker: Erik Petersen

If you search for a useful overview about usability methods, look at this table:

Usability Methods Table by UsabilityNet

FZI Forschungszentrum Informatik Karlsruhe conducting a scientific study, to understand problems and practices of knowledge sharing in software development.

>> Survey <<

Google and David Allen present a interesting video about GTD:

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.