To Team or not to Team? If you look at the definition of Kanban or Lean, you wouldn’t find teams anywhere there. If you look at the Agile Manifesto, you can find “The best architectures, requirements, and designs emerge from self-organizing teams” Scrum is quite clear about the topic (Quoting the Scrum Guide 2011) “Scrum …
A couple of months ago I ran into Think Testing – a new magazine for testers in israel (published in Hebrew). I found it very interesting, and decided I want to contribute. My article has been published in issue number #3. It tries to provide some insight on the experience of a tester when his …
For those interested in my talk about Secrets of Flow, here it is: [slideshare id=7598563&doc=yuvalyeret-flowforagileil11-yuval-v1-0final-110412053436-phpapp02] see some pictures from the event as well:
What is the basic role of the Product Owner? http://blog.crisp.se/2012/10/25/henrikkniberg/agile-product-ownership-in-a-nutshell (New) http://scalingsoftwareagility.files.wordpress.com/2009/11/ch-11-role-of-the-product-owner-rev-12.pdf http://www.agileproductdesign.com/downloads/patton_product_owner_role.ppt Starting with user stories: User stories are the most common way to handle requirements in the agile world. One of the first things you’ll need to do as a product owner is familiarize yourself with them, and start to provide them to …
(Note, this post is about slack the concept not Slack the collaboration platform. Though Slack the platform is great as well. We use it at AgileSparks and love it, although it eats up some of our slack time…) Actually, the title is wrong. I think slack is highly important during any change initiative where you …
