AgileByExample 2016
2016-10-10..2016-10-12
Warsaw, Poland
[AgileByExample 2013, AgileByExample 2016, AgileByExample 2024, AgileByExample 2025]
| title | author | length |
|---|---|---|
| prof. Andrzej Koźmiński - Keynote: Polish Leadership | Andrzej Koźmiński | 50m |
Argues that leadership is fundamentally about coping with constraints and coins bounded leadership, based on ~40 global executive interviews then a… | ||
| Keynote - Focus (or Stop Starting, Start Finishing) | Henrik Kniberg | 44m |
Argues that multitasking makes time‑to‑market 2–3× slower even for a perfect context‑switcher, and shows fixes that actually work: protect one Scrum team, ban… | ||
| Lightning talk – Łukasz Szóstek | Łukasz Szóstek | 04m |
Argues product discovery requires choosing between many small bets and a single big bet using a two‑target metaphor (left target scores 10 points, right 1000… | ||
| Lighning talk | Paweł Brodziński | 09m |
Teams with higher collective intelligence solve complex problems far better than the smartest individual and that metric predicts group performance better than… | ||
| Discussion panel - The Future of Agile | 55m | |
-- no description -- | ||
| So you think you are AGILE - really? | Petter Abrahamsen | 29m |
Argues that agility is a capability, not a ceremony, and breaks it into concrete steps: perceive, comprehend, decide, act executed with speed and energy… | ||
| Social skills for introverts | Marcin Brodziak | 30m |
Claims that everyday social skills become reliable under pressure if trained deliberately, shows two concrete practices: create a weekly YouTube channel to… | ||
| Software Estimation Made Easy | Paweł Brodziński, Tomek Rusiłko | 30m |
Argues that expert guesses and story points fail and proposes statistical forecasting based on lead time and WIP distributions, using historical start/end… | ||
| Creating a culture of continuous improvement | Kevin Goldsmith | 33m |
Leadership joins a scale‑up and spends four months meeting every team, inventorying problems, then replaces arbitrary ship dates with metrics-driven… | ||
| Lessons and Expierience from 15 years of Agile Coaching | Steve Hayes | 28m |
Fifteen years of coaching condense into concrete moves: introduce build lights and daily status emails to restore trust on an $8 million project and still… | ||
| Suddenly reality | Peter Leeson | 36m |
Rapid change initiatives fail because consultants deliver blueprints and audits that create checklists that prove compliance not quality, while day‑to‑day… | ||
| Leading | Andrea Provaglio | 29m |
Argues that leadership in agile is situational and demonstrates it with a workshop exercise using Cynefin quadrants: participants place events (alien invasion… | ||
| Rebooting Agility | Łukasz Szóstek | 29m |
Argues that many software problems sit in different Cynefin domains so apply the right tools: use analysis, experts and upfront plan for complicated problems… | ||
| The magic of timeboxing | Agnieszka Szóstek | 12m |
Uses strict timeboxing to deliver a conceptual design for a 25,000 m², 140 m-long university building in 14 days with a six-person, student-heavy team. Runs… | ||
| Organize your SMs and POs development | Łukasz Aziukiewicz | 15m |
A mentoring framework for developing Scrum Masters and Product Owners uses one-on-one pairs, one-hour weekly sessions, a semi‑formal kickoff to set… | ||
| Effective backlog prioritisation for company happiness | Łukasz Banach | 18m |
Argues prioritisation succeeds when product time is guarded and decisions tie to measurable outcomes: use email bankruptcy and schedule pruning to free white… | ||
| Effective TODO selection: A Kanban story | Adam Cetnerowski | 10m |
Team abandons per-API swimlanes, combines Android and Linux work, and uses a tactile paperboard Kanban with a four-item todo (three product items plus one… | ||
| When devs intend to leave a project and no one knows about it | Jakub Drzazga | 11m |
An NPS survey shows Net Promoter score -12.5 and one-on-one interviews reveal half the core devs planning to quit within weeks; five days of company-wide data… | ||
| The 4 Hours Scrum Master | Tomasz Dzierżek | 14m |
Claims sustained success running four teams while spending about four hours a week on Scrum Master work, proven over two years. Techniques: deliberate absence… | ||
| Building an engineering culture | Marek Kirejczyk | 14m |
Company builds a recruiting puzzle called hack room that gets 11,000 visits, ~4,000 unique users, 1,200 completed games, players from ~100 universities and 65… | ||
| The wisdom of crowds - an aspect of sprints you count on | Radek Lont | 15m |
A live experiment has the audience write three numbers and shows that aggregated independent guesses beat lone experts: Galton’s 1907 ox estimate lands at… | ||
| Taming the Moloch | Andrzej Łach | 13m |
A large retail group with 30,000+ people and 16.2 million customers uses a threefold approach to tame its complex organization and five hundred plus… | ||
| Will anteater survive? | Sławek Łukjanow, Maciej Wilmiński | 13m |
A rolebased simulation called Agile Zoo pairs teams with zonal backlogs (African section, Aquarium, Insectarium), a small shared budget and a dedicated… | ||
| DevOps transformation tailored to organizational culture | Tomek Pająk | 19m |
Uses the Cameron and Quinn survey to map teams as clan, adhocracy, market or hierarchy and shows that success depends on that starting mix. Builds SRE and… | ||
| Why not Agile? | Kuba Ruiz | 13m |
Reports from Poland show only three agile teams or lawyers while counsel has worked on 80–100 large IT projects and found none agile. Main barriers are… | ||
| Keynote: Managing for Happiness | Jurgen Appelo | 53m |
Claims seven concrete practices increase learning and productivity, listing seven silver bullets (food+celebration, playfulness, experiments, managing the… | ||
| UX research in a huge agile project | Małgorzata Wyczańska | 15m |
A new responsive e‑banking platform is built across four countries with 45 sprints planned and releases roughly every 5–7 sprints; two internal releases… | ||
| Visualization to the rescue | Bartosz Zbierajewski, Wojciech Buras | 17m |
A consolidated visualization board built on JIRA — the PJF backlog — maps 40 products (30M LOC) and 60 components across seven communities so teams see where… | ||
| Spotify Running: Lessons learned inside a big tech company | Brendan Marsh | 27m |
Hypothesis: a unique running experience increases registrations and yields higher six‑month retention; team runs 3–4 design sprints (Oct–Dec) using lean… | ||
| Delivering value agility in a large company | K. Niewiński, M. Srebrny | 15m |
Claims a five-step method that starts by discovering a measurable why (goal: at least one valuable release per month), uses corkboard root-cause mapping and a… | ||
| Agility at scale: building feature teams for huge products | Jacek Bochenek | 15m |
Nokia telecom products show that feature teams work at scale but only with a specific path: an IPa platform run by 500 people across Finland and China tries a… | ||
| Designing Agile HR is not a walk in the park for rookies | Riina Hellström | 25m |
Argues that HR must be redesigned to support agile organizations rather than bolted on, using people operations practices, agile and lean methods, and process… | ||
| Lightning talk – Jakub Szczepanik | Jakub Szczepanik | 06m |
A new job portal agile24-7 shows Polish demand for agile roles rising from four to 17–22 offers concurrently, with some postings listing salaries like… | ||
| Is Spotify a good example? | Marcin Floryan | 27m |
Argues that the “Spotify model” is a two-page model not a blueprint and that many read it but few (about half have seen it, ~10% apply it) actually implement… | ||
| Lightning talks – 101 Things Software Never Learnt | Marcin Floryan | 08m |
Argues that applying building-architecture myths to code causes brittle designs and bloated constructors with dozens of dependencies; claims real architecture… | ||
| Lightning talks – Refactoring life | Marcin Floryan | 06m |
Argues life can be refactored like code: first check does my life compile by asking if today is how one wants to spend a last day, then sell the house, pack… | ||
| From big to small and back again | Gus Power | 29m |
Argues that high-quality delivery (continuous integration, CD, XP, automated tests) still fails when context is missing, showing concrete failures: a CRM… | ||
| Not-So-Greenfeld Agile Implementations | Krzysztof Dąbrowski | 26m |
Large enterprises like a big bank and mBank force tradeoffs: enforcing practices first often produces agile values later; permanent scrum masters tend to… | ||
| Purposeful Agile | Oana Juncu | 28m |
Argues agile adoption has three concrete stages: the agile ghetto (teams ship but stay siloed), agile despair (mindset work and coaching expose resistance)… | ||
| Lightning talk – Jurgen Appelo | Jurgen Appelo | 10m |
Claims that organizational change scales if turned into a competitive game where teams earn measurable points for passing concrete tests: a purpose test (ask… | ||
| So far so good... so what? The legal side of Agile | Łukasz Węgrzyn | 27m |
Insist on a written Exit Plan and a short trial period (Sprint zero) so teams can walk away cleanly; give the product owner a legal power of attorney to make… | ||
| Gaining speed | Jakub Uniejewski | 14m |
Reorganized into cross-functional opportunity teams that own features end-to-end and stop passing work through handoffs, the group cuts time-to-value and… | ||
| How many customers do we need and how? | Ivana Gancheva | 22m |
Customer collaboration proves decisive: a Norway government program with 140 million euro program, 175 participants, 12 co‑located teams and 30 domain experts… | ||
| Specification nightmare | Izabela Kowalik | 11m |
Fixed-price, three-year project with ~30 people (7 client, 22 dev) has sprawling, contradictory requirements—stories with 30–40 acceptance points and many… | ||
| Salary Formula: A way through the minefield | Grzegorz Kemski, Karol Sarnacki | 12m |
A simple spreadsheet becomes a public mathematical salary algorithm that maps 9 skill levels to base pay, applies technology multipliers, adds tags for impact… | ||
| Keynote: Out from under the Thumb of Silicon Valley | Brian Marick | 47m |
Argues that agile success depends on embodied skill or meatus learned by apprenticeship not checklists and that coaching supply grows linearly while demand… | ||
| Lean Inspections | Rolf Goetz | 22m |
Case study of a greenfield system with ~100 high‑level themes and a five‑person SME pool uses statistical sampling inspections (300‑word pages, 3 rule checks… | ||
| The systemic Scrum Master | Marc Loeffler | 26m |
Claims that Scrum fails after about six months unless teams are rebuilt around real human factors, not tools; suggests using systems thinking techniques like… | ||
| Effective meeting facilitator | Mariusz Sieraczkiewicz | 14m |
Offers concrete facilitation moves: a quick stand‑up breathing and environment scan to boost presence, a 5‑minute after‑meeting retrospective and simple… | ||
| Creating a knowledge-sharing culture | Jakub Nabrdalik | 17m |
Starts weekly/Friday lectures, a newcomer wiki and a zero hidden knowledge policy so knowledge leaves employees with documented pages and onboarding links… | ||
| Can You scale-down with dignity? | Ewa Koprowska, Krzysztof Biernat | 12m |
Concrete plan to shrink a 500-person program down to 100 while still shipping releases and keeping product quality: set one objective — deliver July 2017… | ||
| nothing matches | ||