inside-scrum

Dienstag, 12. Dezember 2006

Ken Schwaber

Von jp um 21:57
Tags: Regeln, scrum, Scrum Master, User Acceptance Testing, video

Keine Kommentare:

Kommentar veröffentlichen

Neuerer Post Älterer Post Startseite
Abonnieren Kommentare zum Post (Atom)

Wer schreibt hier?

Wer schreibt hier?
Developer. Early adopter. Team leader. Working with Big Data. Works @sentric_ch. Co-founder of SWISS BigData User Group | Zürich

Twitter Radio

    follow me on Twitter

    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) 69er (12) according to specification (1) Africa (1) agil (1) agile (28) 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) ausbildung (1) automatisieren (2) barcampbodensee (1) BayXP (1) Begriff (2) behavior (1) 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) calendar (1) Canoo (1) case study (2) ccmenu (3) CCTray (1) Certified (1) checkout (1) Cisco VPN (1) CITCON (1) CNN (1) CNNMoney (1) Command Line (1) Community-Driven ommercial Development (1) conference (1) consulting (1) continuous integration (2) continuous testing (6) Controller (1) cost (1) crontab (1) CRUD (1) cruisecontrol (2) CSM (3) D620 (1) daily scrum (12) deadline (1) Dell (2) Demo (4) Dependency Injection (1) deployment (2) design (2) DevZuz (1) Disziplin (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) Erfahrung (5) erfahrungsautstausch (3) Erfahrungsbericht (3) Erfolg (2) ergebnisse (1) eric doernenburg (2) estimation (11) experteninterview (2) fahrplan (1) fail (1) Fake (1) Feature (1) feisty fawn (2) fibonacci (1) FIT (2) FIXME (1) Fragebogen (1) Frederick P. Brooks (1) Future of Software Development (1) Gastbeitrag (2) get excited (1) Glay (1) glossary (2) google (4) google calendar (1) Grid Computing (1) grouplet (1) Guidewire (1) gutsy gibbon (1) hal (1) helpdesk (1) high moon studios (1) Hindernisse (2) Hühner (2) ibm (2) ideo (1) IMD (2) Impi (1) infrastruktur (1) Installation (3) integration testing (1) internet-briefing.ch (2) ipod (3) IT Projekt (1) Iteration (4) iterativer Wasserfall (2) itunes (1) Jahresrückblick (1) javascript (1) Jens Korte (1) Jiri Lundak (1) JMock (1) julie bick (1) JUnit (2) Kano (2) Karriere (2) ken schwaber (2) kerstin bücher (1) klassisch (1) Konstanz (1) Konzipieren (2) Kostenberechnung (1) kunde (1) Kurse (1) labcamp (1) Language-oriented Programming (1) large projects (1) Latitude (1) lean software development (1) Leipzig (1) lernen (1) Lessons Learned (5) Linie 908 (1) linux (2) Literatur (3) locale (2) locale resolving (1) loewenfels (1) Lokalisierung (1) Lotus Notes 8 (2) mac (3) MacBook (1) maven (2) Mike Cohn (2) milestone (1) Mock (2) Model (1) Mountain Goat Software (1) münchen (1) MVC (1) namics (13) nein sagen (3) Obeya (1) offshore (1) Omnibusnetzes (1) on budget (1) on time (1) one laptop per child (1) onSoftware (1) ools (1) OpenQA (1) Orbit-iEX (3) OS X (1) Persona (3) Peter Stevens (4) Phyllis (1) pitfalls (1) Planning (4) Planning Meeting (10) Planning Poker (1) planung (2) plug-in (1) Podcast (1) POSTBACK (1) PragmaticQA (1) preoccupations (1) Prinzipien (3) probleme (1) Product Backlog (2) Product Manager (2) product owner (7) project (1) project review (3) projectDE (4) ProjectZero (3) prototyping (1) publisherconnect (1) RAD (2) rails conference (1) RAM upgrade (1) rapid application development (5) rational unified process (1) Read/WriteWeb (1) real days (1) Regeln (4) Relase (1) Release (8) Releasemanagement (3) Requirement Management (1) resourcen (4) RESTful (1) RESTfull (1) Retrospective (11) review meeting (1) RIA-Konferenz (2) roter Arnold (1) RSS Aggregation (1) rubyonrails (2) rup (1) saf (1) sbb (2) Schweine (2) scrum (44) Scrum Einführung (5) scrum in the enterprise (1) Scrum Master (10) Scrum Rollen (1) Scrum Team (3) scrumbreakfast (13) scrumday (1) seeflu (1) selenium (4) 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) Spring MVC (3) SpringOne2008 (1) sprint (3) Sprint 0 (1) Sprint 1 (5) Sprint 2 (2) sprint 3 (2) Sprint 4 (1) Sprint 5 (2) Sprint Backlog (2) sprint burndown chart (5) Sprint Zero (4) sprint-it.de (2) Stadtwerke Konstanz (1) stakeholder (1) state (1) Statistik (1) Store (1) story point (2) Stuart Read (2) Stub (1) Subclipse (1) Subcontractor (1) subversion (1) SUT (1) swissICT (1) Syndato (1) szenario (1) tag (2) target process (12) taskboard (1) tcamp (1) TDD (5) team (4) Test Director (1) Test Doubles (2) test driven development (1) Test Driven Development (1) theServerSide (8) time-to-market (1) tinyPM (1) TODO (1) tools (7) top 10 (1) Top 5 (1) trac (2) training (3) Tristian Woerth (1) trunk (4) Ubuntu (6) Umfrage (3) usability (1) use case (1) User Acceptance Testing (5) User Story (9) Valdieriung (1) Veränderung (1) version 2.5 (1) video (16) View (1) virtueller server (1) VisionOne (1) visual studio (1) Vorgehensweise (1) Vortrag (3) wann agile (4) Wasserfall (3) 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 (8)

    Woran ich arbeite?

    Was bloggen andere?

    Was war einmal?

    • ►  2009 (15)
      • ►  Oktober (4)
      • ►  September (1)
      • ►  Mai (3)
      • ►  April (2)
      • ►  März (1)
      • ►  Februar (4)
    • ►  2008 (72)
      • ►  November (1)
      • ►  Oktober (1)
      • ►  September (6)
      • ►  August (3)
      • ►  Juli (14)
      • ►  Juni (9)
      • ►  Mai (7)
      • ►  April (11)
      • ►  März (1)
      • ►  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)
        • Literatur
        • Ken Schwaber
        • Sprint 2 Retrospecitve
        • Scrum Master
      • ►  November (2)
      • ►  Oktober (9)
    Design "Awesome AG". Designbilder von TommyIX. Powered by Blogger.