Keynote: Unicorns, krakens and self-organized-teams
 |
| a delegation board |
Morning Sessions
 |
| Gil on #NoEstimate |
Meanwhile I missed, among others, Uri Nativ's "Missing Lecture" about the difficult-to-deal-with gap between the agile coach/leader's perspective and the teams' view on the agile change initiative. I love the slides (form and content).
Next, Lior Friedman, talked about code smells, and their less (in)famous cousins: Test Smells. Learning to identify them can help improve the system. After all, TDD is a way to write well designed software. Problems in the tests often tell you of problems in the design, or even in your process.
In a session I missed, Yuval Yeret (happy birthday!) gave a talk about an effective way for managing an agile transformation.
Andrea Darabos conducted her "Lean Lens" workshop. It is essentially a role playing game each team gets a scenario to play out. Some participants act, simulating the different roles, while others observe, trying to identify the 8 types of waste (better known as the 7 wastes + unused skills).
You can download the game here (developed by @bazila and @ADarabos)
Interesting takeaway - try set up a board in the team room to collect instances of the 8 wastes as they happen, and deal with them in the retrospective. Hey - these are "process smells"!
Meanwhile, Eyal Golan talked about working with legacy code. I was told it was interesting and practical.
The last track session actually had 5 options, because Angel agreed to give an improvised sketching workshop where we practices some basic shapes, faces, stick men, containers, call-outs, etc. That was fun, and it was similar to some of Angel's Drawing 101.
More advanced stuff can be found in learning to sketch on tumblr.
Slides here (well, very similar to the ones he actually used). Another interesting concept he described was "job to be done" (JTBD) as an alternative to user stories formulation, focusing on the human need you wish to fulfill. As an intro to the topic, Alan Klement's description of a "job story" is very useful.
There was much more, obviously, but that's what I can share. Great stuff, community!
You can find more here:
Next, Lior Friedman, talked about code smells, and their less (in)famous cousins: Test Smells. Learning to identify them can help improve the system. After all, TDD is a way to write well designed software. Problems in the tests often tell you of problems in the design, or even in your process.
Afternoon Sessions
Three short sessions: |
| One of Barak's slides |
- Gull Ben-David (from MyHeritage) shared why QA people make good scrum masters
- Ran Deri and Noam Zweig (from CyberArk) gave some insight on their experience dealing with Technical Debt systematically. Interesting mix of tools (such as sonar) and assessment (using a survey by Gil Broza) to actually track, negotiate budget and set goals.
- Barak Benjo (Cisco) gave tips for Agile Testing in a legacy environment
In a session I missed, Yuval Yeret (happy birthday!) gave a talk about an effective way for managing an agile transformation.
 |
| "Lean Lens" - observing our results |
You can download the game here (developed by @bazila and @ADarabos)
Interesting takeaway - try set up a board in the team room to collect instances of the 8 wastes as they happen, and deal with them in the retrospective. Hey - these are "process smells"!
Meanwhile, Eyal Golan talked about working with legacy code. I was told it was interesting and practical.
The last track session actually had 5 options, because Angel agreed to give an improvised sketching workshop where we practices some basic shapes, faces, stick men, containers, call-outs, etc. That was fun, and it was similar to some of Angel's Drawing 101.
More advanced stuff can be found in learning to sketch on tumblr.
Closing keynote: Claudio Perrone on Popcorn Flow and A3 thinking
Claudio, a.k.a Agile Sensei, described his A3 thinking / problem solving system, and POPCORN flow, which is a kanban board for capturing, planning and tracking change experiments.Slides here (well, very similar to the ones he actually used). Another interesting concept he described was "job to be done" (JTBD) as an alternative to user stories formulation, focusing on the human need you wish to fulfill. As an intro to the topic, Alan Klement's description of a "job story" is very useful.
There was much more, obviously, but that's what I can share. Great stuff, community!
You can find more here:
- Dror Helper's impressions of the conference here
- Gil Zilberfeld shares some stats (and a creepy photo holding Dalia's disembodied head)
- Twitter handle: #APIL15
