AgileByExample 2013
2013-10-16..2013-10-17
Warsaw, Poland
[AgileByExample 2013, AgileByExample 2016, AgileByExample 2024, AgileByExample 2025]
who it's for
agile coaches, scrum masters, product managers, engineering managers, software developers, technical leads
topics
planning poker as protocol; walking skeleton delivery; continuous integration; test-driven development; kanban WIP limits; code review practices; technical debt remediation; release planning and horizons; organizational experiment backlog; flat company governance and decision making
| title | author | length |
|---|---|---|
| report and summary | Tomasz Szymański | 03m |
A brief report on AgileByExample 2013, a three-day Agile conference in Warsaw that brought together 290 attendees, 18 speakers (plus lightning talks) and 12… | ||
| Planning for Uncertainty | Marcin Czenko | 29m |
Argues that time estimates die beyond one sprint or two horizon because individual task estimates follow wide distributions and velocity only signals trends… | ||
| Software Craftsmanship | Sandro Mancuso | 39m |
Argues that Agile rituals replaced technical rigor, causing chronic technical debt and slower delivery: teams add work to a technical backlog instead of… | ||
| keynote | Jeff Sutherland | 01h 04m |
Scrum expands from software into education, agriculture, government and enterprise with concrete results: advertised Scrum jobs jump from 20,000 to 700,000 in… | ||
| lightning talk – Piotr Burdyło | Piotr Burdyło | 09m |
Four concrete moves: find courage to leave the comfort zone and rehearse in front of harsh colleagues (speaking to ~300 people), craft killer titles and tight… | ||
| lightning talk – Andy Brandt | Andy Brandt | 09m |
Argues corporations are inherently dysfunctional: built for repeatable industrial-scale output, they reward disengaged shareholders and disinterested workers… | ||
| lightning talk – Karol Traczykowski | Karol Traczykowski | 06m |
Claim: stop treating job descriptions as borders and forget your title — take concrete actions to make things happen. Examples: challenge a PO with specific… | ||
| lightning talk – Kate Terlecka | Kate Terlecka | 06m |
Claim: using carrot and stick techniques (treats, rolled newspaper, punishment) produces obedience and compliance but not engagement. Example: Cesar Millan… | ||
| lightning talk – Paweł Wrzeszcz | Paweł Wrzeszcz | 05m |
Software Mill is a 20 person remote company that in June adopts a completely flat structure with 20 people, full financial transparency and no managers… | ||
| lightning talk – Jurgen Appelo | Jurgen Appelo | 08m |
Argues that money matters not as villain but as enabler, citing science that many people 60–90% overestimate their contribution so equal bonuses demotivate… | ||
| Are we agile yet? | Tomasz Włodarek | 21m |
Argues that enterprise agility is an outcome, not adopting Scrum rituals, and recommends treating organizational change as short iterative experiments using… | ||
| My first five years with Kanban - harsh lessons on the quest... | Paul Klipp | 28m |
Built an online kanban board in 2007–2008 to try Kanban; initial Scrum habits create a “plunging” burndown that hides problems until week two. Tight WIP limits… | ||
| Code review, do you speak it? | Michał Ostruszka | 29m |
Compares concrete review workflows and tools: pre-commit vs post-commit, lightweight web review tools and email threads, and when to require approvals from a… | ||
| Stickies on the wall will not help you if... | Wiktor Żołnowski | 29m |
Claim: corporate Agile rituals fail if code quality and technical practices are missing. Evidence: teams using Scrum or Kanban still stall because they keep… | ||
| Agile in the lab | Iwona Cymerman | 17m |
The lab adopts Pomodoro timers and runs daily stand-ups for one month to test uptake, cutting procrastination on writing tasks and surfacing specific chores… | ||
| Five-Spice Scrum in Allegro Group | Jakub Szczepanik | 29m |
Allegro Group runs 60 Scrum teams and reports practical patterns: start by improving waterfall where full Scrum is too risky, then evolve toward Scrum; use… | ||
| Building Teams: We Got It All Wrong | Paweł Brodziński | 27m |
Claim: team performance tracks collective intelligence not the highest individual IQ; Woolley et al. find little or no correlation between individual… | ||
| Get agile and don't die trying | Michał Prządka | 26m |
Two years of moving an eight‑person internal team from ad hoc delivery to disciplined agile produces concrete rules: start with weekly one‑hour retrospectives… | ||
| Scrum Buts - and how to remove them | Joy Kelsey | 16m |
Lists ten common “ScrumButs” and fixes: third-party vendors claiming agile refuse planning or docs so ask for product backlog and sprint cadence; separate dev… | ||
| Technical Excellence: Why does it not stick even now? | Antti Kirjavainen | 27m |
Argues that common fixes fail with concrete failures: a 60% coverage rule that is satisfied by tests with no asserts, a 3 months acceptance + 6 months warranty… | ||
| Are we there yet? Or what a release plan is for | Malcolm Peacock | 17m |
Company Totaljobs runs seven Scrum teams including one in Poland and uses a release plan like a sat nav analogy that outputs an estimated number of sprints, a… | ||
| How I Became a Spaceship Commander | Tomasz Borowski | 21m |
Built a small web app called uGame that synchronizes with YouTrack and rewards developers for completing properly granular, up‑to‑date tasks; rolled it into a… | ||
| Agility is the Tool, not the Purpose | Tom Gilb | 01h 07m |
Argues that agility must deliver measurable stakeholder value not just working code and shows concrete practices that work: the Evo method for managing many… | ||
| nothing matches | ||