Showing posts with label agile. Show all posts
Showing posts with label agile. Show all posts

Tuesday, September 2, 2014

Sarajevo Special Scrum.org Product Owner Training






Studies* show that certain memories help us learn and remember more effectively. Combine a course with a team building exercise, an appraised movie, and you have something amazing - a training with lasting impact. 

This is exactly what we wanted to achieve with the first Bosnia Agile organised Scrum.org Product Owner training.

The PSPO (link) training was build around two events, the Sarajevo Film Festival  and a rafting team building exercise. It does not come as a surprise that this event was sold out 6 weeks ahead.

Between watching a great movie 'The Railway Man' and rafting in this beautiful region, the students where also learning everything important about Scrum, value, lean and agile product ownership. Since I was the trainer it might sound pretentious from me to say how awesome this training was, but in all modesty, it truly was. It was an outstanding and new experience not just for myself. I made many friends and shared many great moments with my fellow students. I am sure that Sarajevo played a big part in this. Sarajevo, the capital of Bosnia-Herzegovina, is a very dynamic and friendly city surrounded by beautiful nature and with good reason was the host for the ’84 Winter Olympics. I for myself cannot wait to go there again.

25 happy Product Owners and a happy trainer cannot be wrong. We have been so pleased that the organisers and I decided to repeat this setup once again next year.

If you live somewhere in the EU you should consider combining education with worthwhile memories. More training content will stick and even better, you will have more fun learning. Consider this: even with budgeting in the costs of transportation and accommodation, it is probably still cheaper than your near-by training provider.

See you next year at the 21st Sarajevo Film Festival …

 

*)

Wednesday, January 15, 2014

The Antibiotics of Software Engineering - Agile Testing


Surgery is not a recent invention, it dates back millennia. 

Notable Milestones in Surgical History (http://surgery.about.com/od/surgeryinthemedia/a/HistoryOfSurgeryTimeline.htm)

6,500 B.C.E. - Skulls found in France show signs of a rudimentary surgery called trepanation, which involves drilling a hole in the skull.
1540 C.E. - English barbers and surgeons unite to form The United Barber-Surgeons Company. These barber-surgeons performed tooth extractions and blood letting. Physicians were considered an entirely different profession, treating illness with medications.
1818 - First transfusion of human blood.
1843 - First hysterectomy performed, in England.
1843 - First use of ether.
1867 - British surgeon Joseph Lister publishes Antiseptic Principle in the Practice of Surgery, extolling the virtues of cleanliness in surgery. The mortality rate for surgical patients immediately falls.
1885 - First successful appendectomy performed, in Iowa.
1890s - Widespread use of chemical agents to minimize germs. Carbolic acid was put on incisions to minimize germs and decrease infection rates.
1896 - First successful heart surgery performed, in Germany. Surgeons repaired a stab wound in the muscle of the right ventricle.
1905 - First successful cornea transplant.
1917 - First documented plastic surgery performed, on a burned English sailor.
1928 - Antibiotics discovered.
…

Even if the procedure was successful, often the patient suffered and usually died of subsequent infections. 
Also, not to ignore is the discovery of Ingnaz Semmelweis, a physician at a Vienna hospital. While working at a Vienna hospital in 1847 he discovered that far more women died after childbirth by the so called childbed fever in the medical ward then in the midwifes ward. Semmelweis postulated the presence and spreading of germs causing the illness by doctors. Even though, after applying a chlorine and lemon based hand-wash solution the death rate could be reduced from ~35% to 1%, he was being labeled a heretic by the doctors. Ignaz Semmelweis was ignored until Louis Pasteur confirmed the germ theory.

Now, after it was accepted that germs caused infections and that hygiene was mandatory for good outcomes it became also obvious that there was a need to have a treatment once an infection set in. As listed above, on September 3rd  in 1928 Alexendar Flemming discovered the antibiotic effect of Penecillin and transformed medicine as we know it. Nowadays, antibiotics are used to treat all kinds of infections and antibiotics are prescribed in a preventive manner for many medical procedures. 

In software development we are able to develop rather fast and make significant changes to existing systems quickly. However, after these procedures the system often falls sick, suffering from bugs, side-effects and other ailments. I like to consider these as infections. Those infections even arise after well planned and executed engineering efforts.
The fundamental question is, how can we cope with them or even better avoid them - what is the the antibiotic equivalent in programming?
For me, the answer is: Agile Testing

Agile Testing is the process to validate that new functionality performs correctly and more importantly to verify that the existing behavior has not changed - that no infection has set in.

1. We have proof that the current system is healthy before the procedure starts
2. We are able to monitor the systems health during the procedure
3. We can intervene the moment side effects set in
4. We have proof that the procedure was successful 

A well done Agile Testing strategy is the equivalent to clean medical equipment and antibiotics. 

Monday, June 3, 2013

Leader, your team is not in the meeting room!




Leaders should stop wasting so much time on meetings. First, the meetings for planning how the team will work. Soon after, the meeting for following up on the previous meetings. Then, the combination of people and meetings just explodes. These innumerous s meetings are the biggest waste for leaders.

Instead, a leader should spend time on the ground with the team. Try to understand and improve processes and how people collaborate. Thus avoiding the distant management purely based on meetings.

Make the work and the workflow visible. This is a crucial activity for a leader. Say no to the meeting invites. Instead, spend your time working with the team members. Look for ways to make the process (and the team work) more visible. Make information more transparent. Encourage direct communication. These allows for greater collaboration.

Ask why! Seek to understand what is happening on each workflow step; ask why. Then ask again. Help the team members better understand their work and the reasons behind it. This, plus the visibility will enable them to understand each other, therefore better collaborating towards the common goal.

Time is limited. And you can have a great impact on your team’s work. Say no to ineffective meetings. Instead, spend your time on the ground working with the team.

Monday, April 1, 2013

fire prevention and firefighting




Moving around large Agile projects, I came across a common situation that hinders the team performance.  Individuals cannot allocate time for improving their work (and avoid future problems) because they are constantly firefighting current issues.

It typically happens like this: Someday on the past, the problem has started. Unfortunately, the issue (small at the time) was not clearly identified. It only got enough attention when it was on fire. Therefore the vicious cycle:


Everyone is busy putting out fires -> no time to improve (and avoid future fires) -> more fires


It takes discipline! Finding the balance between fire prevention and firefighting is not easy. You still need the fire sirens. But some experienced firefighters should be out of the fire department before the fire siren alert. Think preventive and proactively!

Monday, August 27, 2012

Agile in the Large-scale GSD: Success or Sudden Death?


Today is the first day of the ICGSE 2012, the7th IEEE International Conference on Global Software Development which is happening at Porto Alegre, Brazil.
In an hour, I will be participating on a panel about Agile in the Large-scale GSD.
The panel discussions will be led by Albert Avritzer from Siemens.

The panel is bringing academics and industry leaders together. Here are the panelists:
  • Darja Smite, Blekinge Institute of Technology
  • Nils Brede Moe, SINTEF
  • Casper Lassenius, Aalto University
  • Paulo Caroli, ThoughtWorks
  • Jude Fernandez, Infosys
  • Miikka Penttinen, Tieto

Thursday, March 29, 2012

Timeline activity for retrospective

Below is a deck for a timeline activity I used on my last retrospective.

Previously I have used this approach for a collocated retrospective. I would draw a timeline on a white board, create 4 areas on the board (people, process, tools/technology, and other), and use two colors of notes (well – green /not so well - gray) to start with, followed by a third color for action items (yellow).

Here is the snapshot of the retrospective activity (this picture was generated by Google Drawing):



Friday, February 3, 2012

Back to the basics: What made this Agile Inception especial?

The following two pictures depict the latest Inception I participated at.








A little bit of history: For the past two years I have participated directly in 3 Inceptions, and indirectly in 5 inceptions. By directly, I mean, I was sitting in the war room for most of the Inception sessions. And by indirectly, I mean, I was participating on the Inception sessions over video from a Nearshore location (onshore is San Francisoc, USA, nearshore is Porto Alegre, Brazil).

I attribute the success of the last Agile Inception to 3 things: collocation, war room, and colorful post-it.

Collocation

Don’t under estimate the value of a face to face interaction. I am currently in Brazil and I am used to having effective meetings over video and phone with USA. I know that technology can bring people closer together, and, perhaps, we can work together without sitting next to each other. However, the face to face during Inception will bring the team together in a way that it will be worth each penny spend for making the collocated Inception a reality.

I compare it to dating and internet dating. Relationship development goes to another level when the whole team is at the same room. Think creatively on how to save on costs. In our case we were able to reduce the collocated period by having a pre-Inception period before the collocate Inception. Spikes, research, data gathering, codebase analysis were the sort of activities we did in the pre-Inception week.

War room

Keep a single room for the team during the intense Inception period: the war room! The room should fit all team comfortably. It must have a clean table and wall space. The room should also have a cabinet or a box with index cards, colorful post-its and pen.

The war room makes the environment for collaborative sessions. It also avoids the waste of time of people moving from one room to another. Another important point is about carrying the information between rooms. You can either carry all hand-written notes (index cards, post-its, flip-charts, etc) and put them back in the wall and tables, or upload them on a digital format and carry it on your laptop. The former option is a waste of time. The later lessens people interaction. There is no replacement for writing on and tearing apart colorful post-it or index cards. Once the information goes to the computer, it will not get back to paper. People interaction reduces as there is nothing on the table to gather around.

colorful post-its

Do not bring a list of existing user stories to the Inception. I am sure there is a list somewhere (excel, Jira, or alike). Use it for reference, but don’t use it for driving the Inception sessions. Print a few copies and bring them to the war room. Let people consume it if required. Try not to read items from a list during a collaborative session. In fact, do not build a list while in a collaborative session.

Group people around colorful post-its. Write and place post-its either on the table or at the wall.. Talk about them. Write a few more. Tear them apart. Make use of colors. Reorganize it. The collaboration from using such basic, low-fi technology— colorful post-its and pen—cannot be matched by any digital alternative (file sharing, projector, spreadsheets, etc).

The picture below depicts a great example from my last Inception. Without a previous encoding, the team decided to use the colored small post-its for personas. User Stories (in green post-its) were placed on white index cards containing numbers and estimated (with notes on the back).


On future posts: user story mapping for driving Inception, and a few notes on Inception facilitation