Blog

Experiencing Self-Selection of feature teams

Lately I had the opportunity and pleasure to facilitate a process of designing cross-functional feature teams in a self-selection process. Self-selection is a facilitated way to let people choose which team to work in. It is surprising how rare this practice is sometimes even considered eccentric while practically it is a simple and fast and produces such great results – well-formed teams with more involved and engaged people.

Why teams self-selection?

It’s a fast engaging process that creates the best conditions for a team to reach high performance.

It’s based on the assumption that with the appropriate context, people will choose to work in a team that they feel will make them be most productive, taking into account the personal relationships with the other team members, the complementary skills they bring and their aspirations for personal and professional development.

Read More »

The Critical Difference Between Backlog and To Do (Kanban, Scrum)

When we build a kanban board to manage our work (either practicing Kanban or Scrum) we usually create a Backlog list (usually the first column) and a To Do list (following the Backlog). I’ve noticed that many times the separation between the two is artificial and people don’t always understand the critical difference between the two. I’d like to discuss it here.

Read More »

The challenges of testers & developers working together in a cross-functional Agile team

One of the significant changes while moving to Agile teams is that testers and developers are now part of the same team.

This change introduces great advantages, as well as some challenges.

The immediate impact is that the testers participate in the Scrum ceremonies and get a better exposure to the product under development, its status, and its fragility. They can therefore detect better potential areas for defect finding, gain better sync for when they’ll get a drop for testing, and can better utilize their plans.

Read More »

Improving Teamwork Through Experiments

A good way to improve how a team works together is to try to run experiments for collaboration. We’ve listed here a set of experiments you may want to try, depending on where your team is in the journey for better teamwork. Each section has a description, a goal for improvement and then the set of experiments that may help achieving the goal.

Read More »

Elbit Agile/Scrum Agile Israel Case Study – Gil Ari

Continuous deployment is a process that encourages developers to push new code to production whenever they can. In this presentation, Itai will explain the principles of continuous deployment and will show how Outbrain can deploy code more than 20 times a day while serving recommendations to top publishers (including USA Today, iVillage, Boston.com, Chicago Tribune, Newsweek, TheStreet, The Boston Globe, and Slate. Hebrew: Ynet, Haaretz, TheMarker, Globes, City mouse, JPost and more).

Read More »

Scrum Reading List

Scrum Reading List User Story Primer by Dean Leffingwell The 8 Stances of a Scrum Master | Scrum.org How to improve your Daily Scrum? Scrum

Read More »

Agile at FiftyOne – Ben Peer

Going Agile via the Fast Lane – How FiftyOne.com switched from quarterly releases to 2 weeks Scrum and Kanban.
Ben Peer shares the story of FiftyOne.com’s transition in the last year. Starting with Scrum, involving the whole team in true inspect and adapt, evolving to Kanban/ScrumBan, evolving team formation and definition of done, adding Agile Testing approaches including ATDD. In parallel, tight collaboration with a remote Product Management team, and usage of an electronic highly visual Kanban board. Ben will discuss the benefits, the challenges and how the team dealt with them, and will provide recommendations to others considering this journey.

Read More »

Informatica B2B Case Study Lecture in Agile Israel

How we do Agile without saying the word ‘Scrum’

During the last 9 months, Informatica’s B2B business unit transitioned to an agile product definition and development mode. Specifically, we selected Kanban as an agile development methodology. In this talk, I will cover our lessons from using Kanban for enterprise software product development, including:

The impact of a cross-geography organization.
Kanban board structure and changes to the board as a learning process.
The use of data that is collected from the board.
Why we decided to introduce the notion of iterations to our Kanban implementation.

Read More »

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience