Blog

Online Campaign: 5 things you can do to help Duchess

March 7, 2010 in news by Clara Ko

French
  1. Check out the site and please give us some feedback
  2. If you are a Duchess member, log in and update your profile
  3. If you are a woman in Java technology and not yet a member, join us
  4. If you are not a member, subscribe to our newsletter – this enables us to reach those who are interested in receiving news about Duchess (members are subscribed by default)
  5. Share the link http://jduchess.org on social networking sites like Twitter, Facebook, Plaxo, Hyves, etc. On Twitter, follow jduchess and retweet our messages, use the #jduchess hashtag

Duchess Community Site Launched

March 7, 2010 in news by Clara Ko

French

Today, we are launching a new website – Duchess Community, a social networking site that enables members to connect with each other across the globe.

Features of Duchess Community include:

  • Friend Connections
  • Rich Profiles
  • Activity Streams
  • Private Messaging
  • Groups
  • Forums
  • Blogging
  • Multilingual Enabled

Each Duchess Chapter is set up as a group, but topic-related groups can be created by any logged in user. Forums can be accessed through groups or through the forum directory.

We are launching with an international audience in mind by enabling the site to be multilingual. For the launch, the site is set up to be displayed in Dutch, French, and Brazilian Portuguese. We are currently working with volunteers to complete the translations and enable more languages. Let us know if you can help.

All users from our old site have been migrated to the new Duchess Community site. If you are already a member, please log in and update your profile. Feel free to browse around the site and let us know what you think via twitter or email: duchess(at)jduchess(dot)org. We appreciate your feedback and suggestions.

Welcome Duchess France

March 7, 2010 in news by Clara Ko

French

Source: http://blog.xebia.fr/2010/03/03/creation-de-jduchess-en-france/

Please join me in a warm welcome to Duchess France – the newest addition to the Duchess Community.

After meeting a few ladies from Paris at Devoxx 2009, the events have been set in motion to create Duchess France. Duchess France is our first chapter outside of the Netherlands and is the first step in globally connecting women in Java technology.

Rough Translation:
What we wish for jDuchess is to build a community where women who work with Java can connect with each other and share their experiences and points of view. We want to build a social network to make women more visible in the Java community, and to enable them to participate at events like the Paris JUG, and other events and conferences. And perhaps also become a speaker and present at these events.

You can get in contact with Duchess France via Twitter, Google Group and LinkedIn. For more info, please contact ellene(dot)dijoux(at)jduchess(dot)org.

Goodies

January 17, 2010 in news by Regina ten Bruggencate

Order your goodies here: http://duchess.shirtcity.com/

Review Fearless Change

November 18, 2009 in blog by Duchess

At JAOO 2008 I was in a tutorial by Linda Rising called Fearless Change. It was a great workshop about how you could use certain patterns to introduce changes into your organisation. It was also the one tutorial I could almost literally recite to my boss over dinner that night. It was so good, that we decided to buy the book about those patterns. It’s been on my shelf for a while, but I finally made some time to read it and summarize it. And the book was every bit as good as the workshop was. If you ever think of changing anything, you’ll want to read this book. It won’t completely change the way you think about the world, most of what is in it is actually common sense. But as they say in the book under pressure you often leave your common sense behind and that’s why they wrote this book, to remind you of your common sense. Below is a summary of the book. (As is my wont I’ve tried to mainly use the authors’ own words.)

Part One – Overview

In part one it is explained what patterns for change are and a possible roadmap through all the patterns is offered.

Chapter one: Organizations and Change

There are three factors that speed up or slow down the innovation-decision process: The Change Agent, The Culture and The People. The change agent is, most likely, you. You need three things to successfully share your idea: your belief in it, the drive to bring it into your environment and some information on how to do it. It’s obvious that culture will have a significant impact on the speed of the innovation-decision process for your colleagues. The process will be easier and faster if the culture support and nurtures new ideas, allows time for people to learn and do new things, is patient enough to support innovations that have benefits on the long term, accepts that a learning curve can be long, and does not consider failure to be a death sentence. But even in the most conservative cultures, small changes can happen. You will simply need a lot more patience because change will be slower. As you set off on your journey, you might want to remind yourself that the entity you want to change is not a thing, but a collection of individuals. Even when a culture is open to change, the people within it will accept the change at different rates. In a normal organization the people are divided into five groups: the innovator – who love change, the early adopters – who are open to change after some serious consideration, the early majority – who tend to follow their peers and accept change after it has been proven succesful, the late majority – who approach new ideas with skepticism and caution, and the laggards – who are the last to adopt new ideas, if they adopt them at all.

Chapter two: Strategies or Patterns

When you give a strategie a good name, it will stick in your mind easier. All these names together give you a language to speak about the strategies. The book uses a specific format to describe the patterns. It starts with the Name, followed by the Opening Story and a Summary of the pattern. Then comes the Context in which the pattern fits, followed by the Problem it solves. Then come the Forces that are in play, followed by the Essence of the solution, and some more information about that solution. Then comes a Resulting Context with positive and negative consequences. And finally some stories with known uses of the pattern.

Chapter three: Where Do I start?

The first few patterns to try are Evangelist, Test the Waters, Time for Reflection, Small Successes and Step by Step. Every change agent begins as an Evangelist, because unless you are really passionate about the new idea, others will not be convinced to leave the tried and true ways and follow you. Only a true and abiding belief can carry you through all the turmoil of the successes and failures you’ll encounter. Trying to change an organization by throwing out the old and wholesale bringing in the new is not advisable. Instead Testing the Wates with a gradual, experimental strategy that begins with a little investigating and experimenting to see if your idea has a chance in your environment has much more chance of succeeding. Time for Reflection suggest taking time out to learn from your experiments so that you can decide what patterns to apply next. This may seem trivial, but is of the greatest importance, as you don’t learn unless you think about what you’ve learned. Small Successes remind us to celebrate even the small things along the way, to keep us energized enough to overcome the inevitable failures we’ll encounter. Finally Step by Step cautions against doing too much and expecting results quickly. Innovations are best spread slowly and quietly, so you can learn from your failures and build on your successes.

Chapter four: What Do I Do Next?

The next step is to spark some influential support for the new idea with Connector, Guru on Your Side and Innovator. You should also recognize the power of Ask for Help and Just Say Thanks. The risk with introducing anything is that you can get caught up in the passion you feel for your vision and pretty soon others see this as “all about you”. Right from the beginning you should enlist others to help you avoid this trap. The Connector pattern describes those people who are valuable assets because they know “everybody”. Once you have a Guru on Your Side (a trusted expert), many who might have been skeptics up to that point will at least show interest in the approach and will be move open to what you have to say. The Innovator pattern tells us that a small percentage of the population likes new ideas and, therefore, is likely to take up the cause and eagerly do what they can to help you. Never forget the help you get from Connectors, Gurus, Innovators, or anyone else who joing your team. When people do something they consider quite ordinary or part of their job and you take time and thank them, they seem quite pleased.

Chapter five: Meetings and More

Some effective meeting patterns are Piggyback, Brown Bag, Do Food, The Right Time, Plant the Seeds, External Validation, Next Steps, Stay in Touch, e-Forum, and Group Identity. The Piggyback pattern recommends that you don’t do any work that you don’t have to. Instead, give your presentation as part of a regularly scheduled activity. If you do decide to schedule your own meeting, try the pattern Brown Bag and have your gathering over lunch time, when most people are free. Attendees bring their lunch and eat during the meeting. The pattern Do Food recommends using food because it is a powerful influencer. The Right Time is another pattern to keep in mind. For example, there are always better times than hitting a team right before a deadline. At the end of every event, consider the pattern Next Steps. Give people something to hang on to. If you have some interesting books or articles about your new idea, use the pattern Plant the Seeds and bring these materials to the meeting. The pattern External Validation is about lookingfor evidence that your suggested change will work from outside of your own organization. As you collect a list of interested people, think of good ways to use the pattern Stay in Touch. One way to stay in touch is the pattern e-Forum, an electronic forum that will allow you to communicate with a large group of people on a regular basis. If there is sufficient interest, at an appropriate point use the pattern Group Identity. Assigning an identity to your change initiative helps people become aware that it exists and what it is trying to do.

Chapter six: Take Action!

The patterns for the next bold step are Just Do It, Study Group and Mentor. The difference between perfection and excellence is that people striving for perfection are trying not to make any errors. People striving for excellence know that it’s impossible to avoid mistakes. So what should you do to learn? The answer is in the pattern Just Do It. Take a step on the path to your goal and learn as you go. Another way to learn more is to find a small group of like-minded folks who are willing to help you use the pattern Study Group. Each member of the group takes turns leading a session and preapring a “lesson”. While you are learning, you can begin to help others using the Mentor pattern. When teams are just beginning to apply an innovation, it can be invaluable to have someone around that knows more than they do, even if it is only a
little more.

Chapter seven: It’s All About People

Changing means interaction with people, the patterns for this are Personal Touch, Tailor Made and Shoulder to Cry On. When you use the pattern Personal Touch, you help each individual understand how the innovation can be useful in his own environment to solve his problems. The pattern Tailor Made adresses the same concern but at a different level. It is about how the innovation can meet the business needs of the organization. Sometimes you will need the pattern Shoulder to Cry On, as the road towards your goal will not always be an easy one. Like-minded people can help, not only to listen, but also to help thrash out possible
solutions to your problems.

Chapter eight: A New Role: Now You’re Dedicated!

In order to make the change effort part of your job we have the patterns Dedicated Champion, Local Sponsor, Corporate Angel, Early Adopter and Early Majority. To make real headway, you will have to have to be able to apply the pattern Dedicated Champion, that is, the change initiative must become part of your job description. The recognition that the change initiative is deserving of this attention will probably come from your boss, this is the pattern Local Sponsor. At some point you will also need the pattern Corporate Angel, so look for opportunities to capture the interest of a high-level executive, who can ensure that your work is aligned with business needs. Early Adopters need to be convince that the idea is useful to the organization, while those in the Early Majority need to be see that others have been successful before they are influenced to try the innovation.

Chapter nine: Convince the Masses

To convince others that change is good you can use the patterns Trial Run, Guru Review, Big Jolt and Royal Audience. The Trial Run is a powerful pattern, because most of the time, for most of us, change is difficult. The magic is in seeing the change as “temporary”. Suddenly, the new approach becomes a smaller threat. Sometimes resistors want data. To show that your idea has benefit for the organization, you can ask some respected individuals or gurus to evaluate it. This is the Guru Review pattern. When you have resources, you can apply the Big Jolt pattern and bring in an outside speaker. This allows you to take advantage of the considerable influence of well-known people. When you combine a Big Jolt visit with the pattern Royal Audience, you provide the opportunity for people to personally interact with the famous visitor.

Chapter ten: More Influence Strategies

Further influence strategies are Hometown Story, Smell of Success, Just Enough, In Your Space, Token, and Location, Location, Location. Take advantage of the experiences of the early adopters and use the Hometown Story pattern. Ask people to share their story in an informal forum where they can just talk about their experience and then interact in a question and answer session. The Smell of Success pattern recognizes that people will be drawn to the innovation when they hear about positive results. When people are asking questions and things are happening, it’s a good idea to keep the work-in-progress visible using the pattern In Your Space. Making sure the new idea is seen throughout your organization will have a positive impact on the rate at which people adopt it. Another way to keep something alive in people’s minds is to use the Token pattern. This simple influence strategy suggests that you hand out something for participants to take with them when they attend an event related to the new idea. As you schedule meetings related to the innovation, consider the important pattern Location, Location, Location. Having a meeting at another location can be a powerful motivator.

Chapter eleven: Keep it Going

It’s important to keep going, so use the patterns Involve Everyone and Sustained Momentum. Use the pattern Involve Everyone to bring in even those who might not have been a part of your original target population. The second equally important pattern advises that you’ll need to keep a Sustained Momentum. Our natural tendency is to stop and rest once things are underway, but we run the risk of losing everything if we don’t keep it going.

Chapter twelve: Dealing with Resistance

The patterns Fear Less, Bridge-Builder, Champion Skeptic, Corridor Politics, and Whisper in the General’s Ear
will help you overcome resistance. The pattern Fear Less urges you to use the skeptics as resources. Listen with an open mind to hear the other side and take the message to heart. No idea is perfect. We need to learn as we go and what better way than by hearing from everyone around us. Using the pattern Bridge-Builder to find the right person to “adopt” a skeptic can allow you to reach those who don’t find you credible. To make sure you have the objections of the skeptics before you, use the pattern Champion Skeptic. Recognize the contribution of a person who is good at looking at the negative side by officially giving him that duty. When there are important decisions to make, consider the pattern Corridor Politics. Politics are here to stay, and experienced change agents know that before a big vote is taken they should contact each individual who is voting to address any concerns or questions. Use the pattern Whisper in the General’s Ear to convince reluctant managers. The primary reason for using this approach is to begin to build a relationship with a high-level manager. While he may never become an enthusiastic supporter, at least he is less likely to block your efforts.

Part Two – Experiences

To illustrate how patterns can be used to introduce something new, this part of the book presents some actual user experiences.

Multiple Sclerosis Society Experience Report

One woman’s effort to build an international organization involved in research and support for patients with MS.

UNCA Experience Report

A medium-sized university introducing a new general education curriculum.

Sun Core J2EE Patterns Experience Report

Sun Microsystems, provider of hardware, software and services, introducing a specialized collection of design patterns.

Customer Training Experience Report

Introduction of a new approach at a large avionics company.

Part Three – The Patterns

This part of the book contains the patterns. In the book the patterns are described in the format as described in chapter two. For the summary I’ll use the list as used in the appendix of the book. (And as can be downloaded from www.lindarising.org.)

Ask for Help

Since the task of introducing a new idea into an organization is a big job, look for people and resources to help your efforts.

Big Jolt

To provide more visibility for the change effort, invite a high profile person into your organization to talk about the new idea.

Bridge-Builder

Pair those who have accepted the new idea with those who have not.

Brown Bag

Use the time when people normally eat lunch to provide a convenient and relaxed setting for hearing about the new idea.

Champion Skeptic

Ask for Help from strong opinion leaders, who are skeptical of your new idea, to play the role of “official skeptic.” Use their comments to improve your effort, even if you don’t change their minds.

Connector

To help you spread the word about the innovation, Ask for Help from people who have connections with many others in the organization.

Corporate Angel

To help align the innovation with the goals of the organization, get support from a high-level executive.

Corridor Politics

Informally work on decision makers and key influencers before an important vote to make sure they fully understand the consequences of the decision.

Dedicated Champion

To increase your effectiveness in introducing your new idea, make a case for having the work part of your job description.

Do Food

Make an ordinary gathering a special event by including food.

e-Forum

Set up an electronic bulletin board, distribution list, listserve, or writeable Web site for those who want to hear more.

Early Adopter

Win the support of the people who can be opinion leaders for the new idea.

Early Majority

To create commitment to the new idea in the organization, you must convince the majority.

Evangelist

To begin to introduce the new idea into your organization, do everything you can to share your passion for it.

External Validation

To increase the credibility of the new idea, bring in information from sources external to the organization.

Fear Less

Turn resistance to the new idea to your advantage.

Group Identity

Give the change effort an identity to help people recognize that it exists.

Guru on Your Side

Enlist the support of senior-level people who are esteemed by members of the organization.

Guru Review

Gather anyone who is a Guru on Your Side and other interested colleagues to evaluate the new idea for managers and other developers.

Hometown Story

To help people see the usefulness of the new idea, encourage those who have had success with it to share their stories.

In Your Space

Keep the new idea visible by placing reminders throughout your organization.

Innovator

When you begin the change initiative, Ask for Help from colleagues who like new ideas.

Involve Everyone

For a new idea to be successful across an organization, everyone should have an opportunity to support the innovation and make his own unique contribution.

Just Do It

To prepare to spread the word about the new idea, use it in your own work to discover its benefits and limitations.

Just Enough

To ease learners into the more difficult concepts of a new idea, give a brief introduction and then make more information available when they are ready.

Just Say Thanks

To show your appreciation, say “Thanks” in the most sincere way you can to everyone who helps you.

Local Sponsor

Ask for Help from first-line management. When your boss supports the tasks you are doing to introduce the new idea, you can be even more effective.

Location, Location, Location

To avoid interruptions that disrupt the flow of an event, try to hold significant events off site.

Mentor

When a project wants to get started with the new idea, have someone around who understands it and can help the team.

Next Steps

Take time near the end of an event about the new idea to identify what participants can do next.

Personal Touch

To convince people of the value in a new idea, show how it can be personally useful and valuable to them.

Piggyback

When faced with several obstacles in your strategy to introduce something new, look for a way to piggyback on a practice in your organization.

Plant the Seeds

To spark interest, carry materials (seeds) and display (plant) them when the opportunity arises.

The Right Time

Consider the timing when you schedule events or when you ask others for help.

Royal Audience

Arrange for management and members of the organization to spend time with a Big Jolt visitor.

Shoulder to Cry On

To avoid becoming too discouraged when the going gets tough, find opportunities to talk with others who are also struggling to introduce a new idea.

Small Successes

To avoid becoming overwhelmed by the challenges and all the things you have to do when you’re involved in an organizational change effort, celebrate even small successes.

Smell of Success

When your efforts result in some visible positive result, people will come out of the woodwork to talk to you. Treat this opportunity as a teaching moment.

Stay in Touch

Once you’ve enlisted the support of key persons, don’t forget about them and make sure they don’t forget about you.

Step by Step

Relieve your frustration at the enormous task of changing an organization by taking one small step at a time toward your goal.

Study Group

Form a small group of colleagues who are interested in exploring or continuing to learn about a specific topic.

Sustained Momentum

Take a pro-active approach to the ongoing work of sustaining the interest in the new idea in your organization.

Tailor Made

To convince people in the organization of the value they can gain from the new idea, tailor your message to the needs of the organization.

Test the Waters

When a new opportunity presents itself, see if there is any interest by using some of the patterns in this language and then evaluating the result.

Time For Reflection

To learn from the past, take time at regular intervals to evaluate what is working well and what should be done differently.

Token

To keep a new idea alive in a person’s memory, hand out tokens that can be identified with the topic being introduced.

Trial Run

When the organization is not willing to commit to the new idea, suggest that they experiment with it for a short period and study the results.

Whisper in the General’s Ear

Managers are sometimes hard to convince in a group setting, so meet privately to address any concerns.

DevDays Amsterdam 2009 Review

November 12, 2009 in events by Duchess

The DevDays event took place in Amsterdam last week, a one day event about software development. Behind it stands Stack Overflow, also known as Spolky’s software Q and A site, and himself of course. My overall impression was not great I have to say. Something that played role in my slight disappointment was the organization itself. I found the venue very small relative to the amount of people, pretty noisy since the catering facility was in the same room and most importantly quite cold; I spent most of the event wearing my jacket. Lunch was ok but the queue was incredibly long and the sandwiches not enough. Nevertheless, to give the organizers some credit, wifi was working fine at all times.

The day began with a very entertaining talk of Joel Spolsky about the debate between simplicity and power. Do we need all these features or is it better to keep it simple but guaranteed to work properly? Bringing Salginatobel Bridge as an example, he praised the combination of elegance and modesty; in other words software should hide its complexity behind a simple and easy to use interface. And what is the drive of humanity to do anything, even to write (good) software? According to Joel it is to become more attractive and increase the chances of copying our DNA :) I would agree with him here!

The next talk was about jQuery. I do not know that much about it, but I got the impression that the talk was more like someone summarizing its documentation. Even thought there were few interesting points, it wasn’t well delivered in order to catch my attention. After this, there was a talk about the QT toolkit, apparently pronounced cutie and not cute after Nokia’s acquisition of Trolltech. The talk pointed out QT’s platform independency, however not supporting for instance the iPhone; at least not yet… Last talk before lunch was a promotional talk of Joel Spolsky about FogBugz. Despite the whole marketing content I was pretty impressed by the capabilities of the tool: automatic velocity calculation, probability estimation of project completion by date, automatic creation of burn-down charts, ability to break a task in subtasks and estimate them instead of the whole task, code review support etc. I would like to give it a try!

The first talk after lunch was about Python. The speaker, Simon Willison, a bash and Python guru gave a live command line presentation, which I actually found really interesting and informative. The most useful tip for absolute Python beginners, like me, is the virtue of the interactive interpreter. You can first experiment as much as you want and then later create the real stuff using parts of your previous attempts, since the complete history is there for you. All in all, for the first time I was really persuaded for python’s benefits.

The following talk was about the Google App Engine. Nick Johnson deployed an application in very little time. One thing I didn’t like about it is the fact that it supports only relational databases at the moment. As far as language flexibility is concerned, it supports anything that can be compiled to Java bytecode with potential of extension in the future. The next presenter, Christian Heilmann, talked about Yahoo Development Network. Even though it wasn’t one of the talks that brought me to the event, I was positively surprised both by the content and the speakers presentation skills. What to take out if this talk? Check YQL, if you haven’t done it yet, an SQL like query language to manipulate data across the Internet.

Finally the day ended with a talk about ASP .NET MVC. Even though the demo was ok, I found the talk a little bit slow, so given the time of the day I spaced out and decided to leave a little bit earlier. Overall, for next year, I would probably give it one more try, but I would pay more attention at the list of speakers. Also, if it takes place in a different venue, it would be a plus.

Duchess heroes

October 20, 2009 in blog by Duchess

One thing I haven’t yet mentioned in my JAOO report is that a lot of those bigshot speakers also Twitter (and blog of course). This gave me an idea for some neat feature for our site: what if we’d use the @jduchess account to follow all our heroes? And then add a page or something that would show those Tweets. That way people like me who don’t like to follow hundreds of people can check what they have to say every now and then, without actually following everybody.

Of course that leads to the big question: Who are our heroes? Who do we want to follow and what are their Twitternames?
So, leave us a comment! We’d love to hear who they are, what they do to earn the title hero and what their Twittername is.

Devnology Community Day

October 16, 2009 in events by Duchess

Bijeenkomsten van Devnology trekken mensen van diverse achtergronden, en veel van deze bezoekers hebben doorgaans zelf diepgaande technische kennis of verrassende gezichtspunten ten opzichte van software development. Op de Community Day willen we deze mensen graag een podium bieden om kennis te delen. Voor de community, door de community. Die ene gast die altijd zo lyrisch is over Ruby? Op deze dag gaat hij laten zien waarom dat is. Wil je een nieuwe taal leren, of voor jezelf beginnen? Op deze dag vind je mensen met ervaring op vele en diverse gebieden.
» http://devnology.nl/nl/bijeenkomsten/details/15-community-day-01

JAOO 2009 recap – Wednesday

October 13, 2009 in reports by Duchess

C++, Java and .NET – Lessons Learned from the Internet Age, and What it Means for the Cloud and Emerging Languages (Cameron Purdy)
The top 10 reasons why Java has been able to supplant C++ as the dominant programming language are: automated garbage collection (meaning you can build libraries without worrying about memory management), the fast build process, the simplicity of source code and artifacts, the binary standards (cross-platform development), dynamic linking (no more dll hell), portability, standard type system (primitive types and java.lang library), reflection (again necessary for making libraries), performance (due to garbage collection and multi-threading), and safety (no more pointers and therefor no more buffer overrruns). On the other hand there are 5 reasons why Java has not been able to supplant C++: Startup time (many classes have to be loaded to run the simplest of programs), memory footprint, full garbage collection pauses, no deterministic destruction, and barriers to native integration. Despite these last five reasons, the shift to Java has been made anyway. Why? Because the internet came along. Suddenly applications were run in a browser and no longer on the client. Suddenly those five advantages C++ had weren’t as important anymore. And then they came up with scripting languages that were a lot more simple as well. Many of these run on Java’s JVM.
But now we are shifting to Cloud computing and that is where Java still misses a few aspects. When it comes to the virtual machine for example, we’re going to need a lower memory footprint and predictable garbage collection pauses. So the conclusion is that either Java will step up to the new challenges or it will get replaced by another language that does.

Guiding Your Personal Life: Plan-driven or Agile (Linda Rising)
Around 1800 the industrial age began in England. Suddenly people moved from the farm to the factory. This change was inspired by many elements. First of all the clock was becoming widespread in it’s use, which gave people an accurate way to tell time, allowing people to make punctual agreements. Second, caffeineated beverages were discovered, replacing beer as the main beverage. As water had to be boiled for making tea and coffee, it became largely safe to drink. This coupled to the rise of factories led to the lifestyle we still have today. This lifestyle, however, isn’t very natural. Until the industrial age the time for sleeping was dictated by the sun, allowing people more sleep in winter when it was neede more. Furthermore, caffeine isn’t very healthy either as it blocks the natural hormone that tells us we are sleepy, meaning we sleep even less. More and more, sleep is seen as something that is a waste of time. While it has been proven that without adequate sleep, we are not at our best, physically, mentally or emotionally. Even worse, without adequate sleep our brains show visible signs of premature aging. Caffeine will make us feel better and have us believe that we perform better, but the effects are no better than what a break would allow. Even more, caffeine only improves vigilance tasks. Tasks that require prolonged attention and little physical activity, like tightening bolts on a production line. And worse yet, for complex tasks only extroverts’ performance improved, while introverts tended to get worse.
Extensive experiments have been conducted that prove that sleep improves our learning capacities. Even just a short nap helps a lot. Sleep is divided up into cycles that consist of several phases. So maybe we should make sure that we use similar cycles for our activities. At the very least we should experiment with these ideas to see what works and what doesn’t.

Organizational Patterns and Scrum: Fine-tuning your Agile Implementation (Gertrud Bjørnvig & Jim O. Coplien)
The presentation started off with a little roleplaying where several people from the audience got a hat with a role attached to it and had to act out what they thought were the distances between them and the other people on the team. Through this play several of the patterns from the book Organizational Design Patterns were shown. After this a short history of patterns was discussed, along with the definition of a pattern and what Scrum is. The statement was that Scrum is very complex and that it should contain a whole slew of patterns, and that if Scrum isn’t working properly for you, you might want to investigate these patterns to find out how they can help you get to where you want to be. The conclusion was that Scrum is a pattern language, where the patterns provide insight and encouragement to fix broken Scrums. The patterns can also be used as an incremental path to Scrum adoption. So if you haven’t read it yet, go read Organizational Design Patterns by Coplien and Harrison, as it contains essential knowledge everybody who wants to change their organization should have.

Deliberate Practice in Software Development (Mary Poppendieck)
In sports and music it is well known that you only get to be an expert if you practice a lot. And not just any practice, but deliberate practice. The four pillars of deliberate practice are having a mentor, being challenged, getting immediate feedback and being dedicated. Mentors in IT should hire and grow people, review and guide work, set technical standards and ensure technical excellence. Unfortunately, most companies don’t have mentors. They usualy assume that product champions are enough. But a product champion is more like a conductor than like a music teacher, necessary, but not enough to ensure quality. In order to be challenged, you should get to do hard things and be able to do them frequently. Only too often you don’t get challenging work assignments as assignments are handed out to the people who are already good at that type of work. And when it comes to feedback the programmers are often kept at arms lenght of the customers, so the feedback is usually indirect. A good example of direct feedback is the feedback you get when you work on an Open Source Project, it is immediate, constant and detailed. And finally, skill development takes time. Time spent in the same place, as rapid job movement doesn’t develop skill. Time to learn without interruptions. Time to invent, practice requires the time to make mistakes.

The IT Division Refactored (Richard Durnall)
After quite a few years as an industry we’re still seeing over 60% of all projects in IT fail. This might be in part due to the way our IT divisions are structured. We are still working in a structure that was pioneered to manage a lot uneducated people. Despite the fact that we’re no longer uneducated and that we’ve known for quite some years that this model is quite inefficient for our current needs. All of this because managers believe that it is better to fail conventionally, than to succeed unconventionally. The current model is to start at the top, appoint managers by specialisation, allocate people to divisions/teams, communicate a strategy, determine performance targets, define the delivery process and then to engage the customer. A better model would be to start with the customer, develop a strategy, design initial processes, define process metrics, structure the organisation to support these processes, appoint process managers, and to end at the top and then to adapt and improve. Things to keep in mind are to improve the process first and only then to automate. Otherwise you will automate things that weren’t working in the first place. You should also allow for change. IT systems are corporate concrete that will freeze the processes. Systems Management Theory resolves the challenge of how to do Agile at scale.

Value Management (Evo) with Scrum development (Kai Gilb)
One of the reasons why selling Agile development to managers is so hard, is that the agile manifesto is all about the developer and not about delivering value to the stakeholders. The value management process contains eight steps: identifying the stakeholders, finding and specifying quantitatively the stakeholder values, prioritizing the possible solutions, breaking the winning solutions into smaller entities and packaging them, developing the packages, delivering to stakeholders, measuring the changes, and finally learning and changing the behavior. Scrum is only about the four steps from solutions to delivery. The value management cycle and the development cycle are both equaly long -1 to 3 weeks- and should take place at the same time. To implement value management you need to determine the business values, refine those in stakeholder values, refining those in product values and turn those in a prioritized scrum list. This doens’t have to be a top-down approach, as long as the end result is that the lists are defined. So if the problem is that a certain service is too slow, the developers are asked to come up with as many solutions as possible to solve this problem and then to present these to management in a value decision table, containing information on how much better the situation will become, how much resources it will cost etcetera. The greatest challenge to get this working is to get the business owners and steering committees to stop thinking in technical solutions. Business owners should instead focus on what their real needs are and the steering committee should sign off on value improvements, so the developers can come up with the best technical solutions that will give maximum product value improvements. Some case studies of where value management has been used show astonishing results.

Duchess Dinner after JFall

October 13, 2009 in events by Duchess

After JFall (11 November 2009) we will have our traditional dinner again in Bussum. Even when you can not attend the conference itself you are still welcome to join us. Just let us know.

Where:

De drie vrienden.

Landstraat 2
1401 EN  Bussum

When:

11 November 2009  at 19:00