inside-scrum

Dienstag, 5. Februar 2008

Agile Estimation, Mike Cohn

Von jp um 13:44

Tags: BayXP, estimation, Mike Cohn, video

0 Kommentare:

Kommentar veröffentlichen

Neuerer Post Älterer Post Startseite

Abonnieren Kommentare zum Post (Atom)

Wer schreibt hier?

Wer schreibt hier?

Hi, i'm Jean-Pierre. I grew up in Niesky near the polish boarder, east germany and went to south west germany in 1992. I finished my studies (Business Information Technology) in 2003 and went to Switzerland ... I'm a software engineer working at namics.com.

Wie kann ich helfen?

Web	inside-scrum Blog

Was lese ich?

Agile Advice, multi-author blog
Agile Alliance
Agile Testing, Grig's blog
All about agile, Kelly's blog
Ed Gibb's Blog
Implementing Scrum, blog
Mountain Goat Software
Scrum Breakfast, Peter's blog
Scrum Log, Jeff's blog
The Scrum Blog, Andy's blog

Label Cloud

.net (1)

.NET User Group (1)

2007 (1)

according to specification (1)

Africa (1)

agile (25)

agile manifesto (4)

agile mentor (4)

agile method (1)

agile42 (1)

agiles projektmanagement (2)

agiles Vorgehen (2)

agilesurvey (1)

agilo (1)

agilo for scrum (2)

aglile (2)

Agnes (1)

Ajax in Action (5)

Alex Iskold (1)

amazee (2)

Amazon (2)

apache (2)

Apache Tiles (1)

automatisieren (2)

barcampbodensee (1)

BayXP (1)

Begriff (2)

Bern (1)

best practice (16)

better builds with maven (1)

bharat mediratta (1)

blog (1)

board (1)

branch (2)

broke the build (2)

budget (1)

Bug (1)

build (2)

Business 2.0 (1)

Canoo (1)

ccmenu (3)

CCTray (1)

CITCON (1)

CNN (1)

Command Line (1)

Community-Driven ommercial Development (1)

continuous integration (2)

continuous testing (6)

cost (1)

crontab (1)

CRUD (1)

cruisecontrol (2)

CSM (2)

D620 (1)

daily scrum (10)

Dell (2)

Demo (1)

Dependency Injection (1)

design (1)

DevZuz (1)

Dokumentation (1)

Domain Specific Language (1)

done (1)

DSL (1)

Dummy (1)

DWR (5)

early adopter (1)

Eclipse (2)

Eigenverantwortung (1)

Einführung (2)

Element (1)

Entwicklungsumgebung (1)

Epic (1)

erfahrungsautstausch (3)

Erfahrungsbericht (3)

Erfolg (2)

eric doernenburg (2)

experteninterview (2)

fail (1)

Fake (1)

Feature (1)

feisty fawn (2)

FIT (2)

FIXME (1)

Frederick P. Brooks (1)

Future of Software Development (1)

Gastbeitrag (2)

get excited (1)

Glay (1)

google (4)

google calendar (1)

Grid Computing (1)

gutsy gibbon (1)

hal (1)

high moon studios (1)

Hindernisse (2)

Hühner (1)

ibm (2)

IMD (2)

Impi (1)

infrastruktur (1)

Installation (3)

integration testing (1)

internet-briefing.ch (2)

ipod (3)

iterativer Wasserfall (2)

itunes (1)

Jahresrückblick (1)

Jiri Lundak (1)

JMock (1)

JUnit (2)

Kano (2)

kerstin bücher (1)

Konzipieren (1)

Kostenberechnung (1)

kunde (1)

Kurse (1)

Language-oriented Programming (1)

large projects (1)

lean software development (1)

Leipzig (1)

lernen (1)

Lessons Learned (5)

linux (2)

locale (2)

locale resolving (1)

Lokalisierung (1)

Lotus Notes 8 (2)

mac (3)

MacBook (1)

maven (2)

Mock (2)

Model (1)

Mountain Goat Software (1)

MVC (1)

namics (9)

Obeya (1)

Omnibusnetzes (1)

on time (1)

one laptop per child (1)

ools (1)

OpenQA (1)

OS X (1)

Persona (1)

Peter Stevens (4)

Phyllis (1)

Planning Meeting (7)

Planning Poker (1)

planung (2)

plug-in (1)

Podcast (1)

PragmaticQA (1)

preoccupations (1)

Product Backlog (2)

Product Manager (2)

product owner (7)

project (1)

project review (2)

ProjectZero (3)

publisherconnect (1)

RAD (2)

RAM upgrade (1)

rapid application development (1)

rational unified process (1)

Read/WriteWeb (1)

Regeln (4)

Relase (1)

Release (8)

Releasemanagement (3)

Requirement Management (1)

RESTful (1)

Retrospective (7)

review meeting (1)

RIA-Konferenz (2)

roter Arnold (1)

RSS Aggregation (1)

rubyonrails (2)

rup (1)

saf (1)

sbb (2)

scrum (40)

Scrum Einführung (4)

scrum in the enterprise (1)

Scrum Master (9)

Scrum Rollen (1)

scrumbreakfast (10)

shell-script (1)

shift (1)

Simple Application (1)

sms (1)

SOA (2)

Software Development (2)

Sommar (1)

sprachabhängig (1)

Spring (2)

Spring Framework (1)

SpringOne2008 (1)

sprint (3)

Sprint Backlog (2)

sprint burndown chart (1)

Sprint Zero (3)

sprint-it.de (2)

Stadtwerke Konstanz (1)

stakeholder (1)

state (1)

Store (1)

story point (2)

Stuart Read (2)

Stub (1)

Subcontractor (1)

SUT (1)

Syndato (1)

tag (2)

target process (12)

tcamp (1)

TDD (5)

team (4)

Test Director (1)

Test Doubles (2)

Test Driven Development (1)

theServerSide (8)

time-to-market (1)

tinyPM (1)

TODO (1)

tools (7)

top 10 (1)

Top 5 (1)

trac (2)

Tristian Woerth (1)

trunk (4)

Ubuntu (6)

Umfrage (3)

User Acceptance Testing (5)

Valdieriung (1)

version 2.5 (1)

Veränderung (1)

video (16)

View (1)

virtueller server (1)

visual studio (1)

Vorgehensweise (1)

Vortrag (1)

web 2.0 (1)

WebTest (1)

Werner Vogels (1)

Werte (1)

wifi (2)

wiki (2)

wlc (1)

workreportr (1)

XP (6)

YouTube (1)

Zertifizierung (2)

zürich (4)

Powered By:Blogger Widgets

Woran ich arbeite?

Was bloggen andere?

Was war einmal?

▼ 2008 (56)
- ▼ Juli (9)
- ► Juni (9)
- ► Mai (7)
- ► April (11)
- ► März (1)
  - Lasst das Team arbeiten
- ► Februar (7)
- ► Januar (12)

► 2007 (114)
- ► Dezember (14)
- ► November (2)
- ► Oktober (22)
- ► September (2)
- ► August (4)
- ► Juli (7)
- ► Juni (18)
- ► Mai (5)
- ► April (8)
- ► März (15)
- ► Februar (13)
- ► Januar (4)

► 2006 (15)
- ► Dezember (4)
- ► November (2)
- ► Oktober (9)