12. May 2013

How to improve complex software system in 10 steps

1. Introduce small change.
2. Wait and watch the impact. It may take some time to proliferate.
3. Learn about consequences.
4. Point out broken old parts which should be removed or replaced.
5. Prepare stubs and fixes.
6. Dry run. Prepare for quick rollback.
7. Repeat steps 4-6 until you’re sure.
8. Detonate the change.
9. Get ready to fix stuff that breaks during aftershocks.
10. Take a break, enjoy new system and learn something new.

28. August 2011

Software Feature Paradox

By adding more features you'll achieve less.
By adding less features you'll achieve more.

Why is this paradox so common in the Sea of Software development?

It’s easier to add more than to add less.

It’s easier to rush than run for a long distance.

It’s easier to promise castle in the air than build it.

It’s easier to blame old code in the system than find understanding.

Is it harder to write test before a code than fix a bug within a bug within a bug?

😉

19. February 2011

Software travelers

Bas Vodde mentioned very interesting technique in his interview for SE-Radio.net. He call this technique travelers.

Let’s consider scenario: product development reached the end of iteration. Teams delivered results. People learned quite a lot. Some of them have very specialized knowledge.

Let’s give opportunity to people with very high technical knowledge to choose their team for next iteration. Give them the badge of traveler. They can choose where they want to travel in the organization.

Some of them will stay. Some of them will enjoy traveling between teams.

This technique can improve flow of knwoledge inside organization.

Software traveler is definitely not a new idea. Companies with wise management are already doing it. What I consider as very important is that Bas Vodde gave it the name.

You can download very good episode of podcast with Bas Vodde from Software Engineering Radio – episode Large Agile Software Development. I really enjoyed listening to this episode. Bas was talking about many interesting concepts in software development and agile.

Bas Vodde and Craig Larman wrote a book with title Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale SCRUM.

Note: You can follow SE-Radio Twitter – @seradio.

  • Where is the fish?

  • Further info

  • Twitter

    Follow @jurajmichalek on twitter.

  • Comments

  • Tags

  • Topics