Summer School Weekly Cartoon: Team Leadership

July 30th, 2010 07:00 am von Joachim Legat · No Comments · Scrum, Summer School 2010

Traditionelle Teamführungsmethoden sind doch super!

Naturally a good team leader always keeps his team in a good mood! And now thanks to the Scrumlies we know how to do this.

We just finished the fourth week of Summer School, which means we are now halfway done. Next week we will cover the topic “Scrum and Contracts” that will be introduced with an exciting article from Marcus Antonius Hofmann, lawyer from Munich.

Have a great weekend and we will see you next week.

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ Write a Comment

Advertisement | ScrumJobs | Product Owner | Berlin

July 29th, 2010 10:01 am von Boris Gloger · No Comments · Jobs, Scrum

Our customer, a well known and succcesful WEB 2.0 Company, is looking for a Product Owner (m/f) in Berlin.

Responsibilities: You are responsible for the development of a sub area. You will use marketing and user analysis to develop sustainable product concepts and to continually improve previous functions based on internal analysis.

You will assume the  leadersip of a dedicated development team, with which you will implement new functions for the platforms using Scrum methodology. You will be the contact person for external development partners, as well as for internal customers in the areas of marketing, sales and software development.

You should have an excellent knowledge of technology and be thoroughly interested in social media phenomenon.

Your competencies and experience:

  • Completed study in a field of  economics or technology
  • At least 4 years of experience in internet product management or as an agent with distinctive technological competencies, especially for front end topics
  • complete understanding of internet business models
  • Excellent knowledge of current analysis tools and outstanding, analytical communication and diplomacy skills
  • Good ability to assert oneself and to work under pressure, Scrum experience is definitely preferred

If interested please contact André Häusling at www.scrumjobs.com: andre.haeusling@scrumjobs.com

This posting is an ad.

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ Write a Comment

Necromancy or Development of the Team Spirit?

July 29th, 2010 07:00 am von Dieter Roesner · No Comments · ScrumMaster, Summer School 2010, Team

What actually makes a “good”  or effective team, for example a Scrum Team? Of course there are many factors that must be present and work together. An essential and desirable element of a “good” team is certainly what in general is called the team spirit (sometimes also group unity). Team spirit is invoked again and again, and the teams are asked to show even more team spirit (in the sense of a more likely moral category).

But still teams have no spirit, especially not in the initial phase. They develop, form and nurture it as a tangible permanent process and when present as a positively experienced, emotional phenomenon. Team spirit is an internal condition, that consists of and develops from a fundemental collegiality of sovereign individuals.

The central basis for this desired process is an experienced growth of esteem, respect, trust, reliability, discipline, security and regarding each other. This team spirit basis develops through working and achieving together to reach common results and secondly through lasting collective and individual successes and feedback on success. But watch out: often individual success must take a back seat for the benefit of the team spirit.

The recognition of individual achievement and success in the framework of team achievement (by the other teammates)  strengthens the individual sovereignty and with it the components of esteem, trust in one another and mutual respect.  Working together and experiencing success  establishes a sense of belonging, of togetherness, solidarity, loyalty, acceptance of heterogeneity, communication and a willingness to accept arguments, and forms a team identity and spirit.

Team spirit becomes more stable  through appreciation in terms of the team context. If a team directly or indirectly hears that it is known as a specific team x/y and is recognized as  such it gets identity feedback. This leads to clarification of the self-estimation, and to a creation of borders against the outside which is necessary for the team spirit. Lateral team leadership i.e. team leadership without direct disciplinary power, or so-called “leadership from the sidelines,” specifically supports the described variables of the development of team spirit (for example in Daily Scrums, Retrospectives, impediment processes, in communicating success to others, etc.). This helps to make stumbling blocks apparent, as well as other obstacles to the development of  team spirit (like too little contact, little or inadequate communication, unresolved conflicts, ego trips, lack of recognition,  blind collectivism  etc.) , and helps teams to work on them specifically.

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ Write a Comment

Case Study: ‘You and Your Scrum’ – When Agile Thinking Hits a Nerve

July 28th, 2010 12:28 pm von Katrin Dietze · No Comments · Scrum, Summer School 2010

In this week on Leadership and Teams in Scrum there is a special Case Study. The Case in this case is a cold one. This time it is not a topical view of somebody’s own company, but a summary of lessons learned. We talk to Jodok Batlogg about his experiences with teams and organization as the leader of a big development team that successfully switched to Scrum with him as CTO.

100728_case study jodok batlogg

We’re awaiting your comments on this topic.
Does this kind of agile thinking hit a nerve with you, too?

Jodok, thank you very much for your time,
I can’t wait to know about your next field of work!
Katrin Dietze, Hands on Design. Webteam

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ Write a Comment

Networking and Social Networks

July 26th, 2010 09:21 pm von Boris Gloger · No Comments · Summer School 2010

Social networks like Facebook, XING, Linkedin, and StudiVZ appeared because a handful of people began to turn a vision into reality very fast. They have succeeded and they have grown and grown. Suddenly these organisations feel the tensions between traditional management and innovative leadership. They were created from an idea, out of an impulse, they became successful, tried out new things, and threw all the rules over board. Mark Zuckerberg seems to be competely averse to following any rule, as I gather from his statements on data protection.

If social networks are successful, and have got their first Proof of Concept over successfully, then they get noticed by investors. The investors bring along their traditional rules of doing business and their traditional controlling-systems. [1]

Suddenly the people in these organisations find themselves confronted by a new challenge. Now they are expected to plan and guarantee success. The people at the top have to justify themselves to their investors.

As if this wasn’t completely illusory in a game that nobody has mastered yet, in a business that didn’t even exist 10 years ago, using technologies that are only just being developed by the people in these organisations.

If this pressure is withstood – in the case of Facebook Zuckerberg refused to sell and remained at the top himself - then the scales go down on the side of innovative leadership. This is not the kind of leadership everyone likes, since often it is quite dictatorial. The advantage is obvious, however: here new things are tried out. Zuckerberg does without road maps and himself creates the new paradigms for his architecture. On one side responsibility goes down as low as possible, on the other side he sometimes simply carries things through.

In other social networks, which were not so lucky as to escape the investors, the scales go down for traditional management. Here there is a demand for innovations, but then they are discussed to pieces in committees and governing boards. Middle management levels are built in, corporate structures created, and traditional reporting systems established.

The problem is, as Dieter wrote yesterday, that there has to be leadership, but at the same time social networks have to find a different kind of leadership from the one taught by traditional management methods, if they still want to be able to innovatively create something new.

And they would be ideally adapted to this, since they have evolved from the paradigm of the network. They have produced the infrastructure which is needed to collaborate over distances, while giving a voice to every individual inside the network, and creating evaluation criteria that allow the community to single out an individual and to appreciate a single achievement. Their evaluative mechanism is not hierarchical and they create leadership through followers. In this way a page or a person becomes a hub for opinions and thus a leader. Seth Godin calls these people the founders of tribes.

What would a vision for social networks look like? Social networks would have to find a way of utilizing these mechanisms within their own structures. This could mean that new features do not come from ABOVE, but are brought into play by employees and users. In that case the employees would decide on the next feature, and they would, if it looked feasible, realize it as fast as possible, and put it into the net.

If the feature was a success, it would stay in the network, if not, it would get dismantled again later. If the feature was so much searched for that more and more services needed to have it, then Management would decide whether to make it part of the functional social network platform. In this way the company would lead the Community in a direction that matches their own vision, and fits the Community.

Unfortunately reality looks different. To my mind, Germany’s social networks are losing their innovative power. They are hampered by traditional business models. Managers demand clear road maps, features have to pay their way, and customers are to get the things they demand. Team-Leaders get drawn in, the first hierarchies come into being, and there is a search for those responsible. There is pressure, not from the group, but from above, for suddenly deadlines have to be kept. Management begins to make deals with managers, without first consulting those who know better. Decisions are made centrally. Social networks turn into something internally that they pillorize externally: a boring, and self-satisfied tayloristic organisation.

It is possible to change this, and to stop this movement. Over the past 3 years we have seen how companies from the early internet age are able to gather momentum again with Scrum, the kind of momentum they had when they first began. I am talking about the big networks and portals in Germany (all the well-known German internet companies use Scrum by now – has Facebook ever tried Scrum? No idea!).

Scrum has offered an ideal start for every company on the way towards a more network oriented kind of working. Scrum has also offered these companies an elegant way out by limiting this kind of work to their development departments. But why? Why is it a problem for graphics designers, product designers, and all those,  to introduce the networking idea to their own departments, and to live with that basis of their existence, the network, inside their own company?

I have no clear answer for this, only an idea. It is a matter of power again. The network dissolves every kind of traditional view of power. Most companies see IT as a service. If I put the service people into a framework that demands more control while taking away power from them at the same time, then I will gain a lot of power. However, to question one’s own position in a network, does not only mean a loss of comfort, but a very real loss of original power. This is the weakness of any network-based strategy, and thus also that of Scrum. Scrum out-of-the-box does not have any profit to offer to middle management that could make up for their loss of power.

Companies that start with Scrum have to ‘think beyond’ Scrum, and have to deal with their structures in a holistic manner.

The day after tomorrow we will see what Jodok Batlogg has to say about Scrum and Social Networks. Let’s look forward to it.

[1] Google, if you read the Google Story aright, has escaped this dilemma because the founders, although they did take the money from the start, never let themselves be  interfered with.

[2] This is what Niels Pfläging calls modern companies  in “Führen mit flexiblen Zielen [Leadership with flexible goals] “.

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ Write a Comment

Team Leadership in Projects – Assigned or Chosen

July 26th, 2010 07:00 am von Dieter Roesner · 1 Comment · Manager, ScrumMaster, Summer School 2010

If you have been following the political process since the last parliamentary election in Germany in 2009, you can observe a fascinating phenomenon:  the media and other “experts” complain about a huge vacuum in leadership and the number 1 reason – the chancellor – has been asked ” to finally start leading”. But somehow this has not succeeded.

This clarifies the specific dilemma in democratic systems: the strong dependence of the leaders on the people being lead, or the voters. Any democratically elected leadership can be voted out of office again (and is influenced by the weekly news of current trends.) Thus  they strive in the interim to keep voters “happy” (see election in NRW) and in doing so lose sight of necessary leadership. But if they are not lead “well”, the voter is again dissatisfied, which leads to a loss in confidence and popularity, not to mention a loss of authority in the leadership team (government, see “Gurkentruppe, Chaosverein, Wildsau” i.e. Cucumber troupe, Chaos Club, Wild boar, etc.) – a real dilemma for political leadership in democratic systems. This “weak point” is counter- balanced by agitation from the opposition, the media, etc., that in this case act as a regulator and prevent a bigger “catastrophe”.

What is the connection between this topic of political leadership and team leadership, i.e. lateral leadership by a ScrumMaster?

Again and again the question is asked (for example also at Scrum Trainings), if it would not make more sense for the sake of self organization, if teams would choose their own leadership (or ScrumMaster).  In my opinion this question is clearly to be answered with no.

Leadership should be defined here as specific and legitimate influence on others (colleagues) in the interest of a higher-ranking system to accomplish definite tasks and achievements. An elected team leadership in this sense inevitably comes to a similar dilemma as political-democratic leadership, or in particular to a strong dependence on team members. The necessary leadership distance is not, or only conditionally guaranteed and therefore limits influence. There is no legitimate regulator (see above),  that in the case of a leadership crisis (i.e. loss of authority or trust, power conflicts, etc.) can clarify the situation in the sense of a higher ordered system specifically and competently.  Observed phenomena then are chaos, neglect, loss of power, and of resolution.

A team leader assigned by management (ScrumMaster) has a legitimate position of power, is not directly dependent on the team (although part of it), and can therefore assume leadership from a distance and execute the necessary influence for the situation. In critical team situations the hierarchical intervention of the “appointed”  team leadership handles (or should handle) the regulative procedure in the interest of solving the problems of the system.  For example through reinforcement of leadership, moderation and through changing the personnel situation.

It is recommended that appointed team leaders perform their function in a confident manner without a “guilty conscience”, as in this case they are a genuine part of the self organization of a team. It is also advised that the appointee is conscious of their role as regulator, so that they can intervene competently and with a definite goal when needed.

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ 1 Comment

Summer School Weekly Cartoon: Communication

July 23rd, 2010 08:00 am von Joachim Legat · No Comments · Scrum, Scrumlies Stories, Summer School 2010

Die Scrumlies zum Thema "Kommunikation" ;-)



The Scrumlies, too, know how to cooperate within a team: you spell Communication with a capital C … and leave it at that :-)
And they all do what they want, nobody does as they should, but  everybody takes part.

This was Summer School Week 3 on ‘Communication and Moderation’.

Next week we will look at Team Leadership and Team Development. The editorial on Monday will pose the question whether the team leader should be elected by the team or assigned to it by somebody else. We all wonder what your opinions are about this …

Share and Enjoy:
  • Facebook
  • Twitter
  • PDF
  • RSS
  • email
  • LinkedIn
  • del.icio.us
  • Digg
  • StumbleUpon
  • Google Bookmarks
  • Identi.ca
  • Reddit
  • Technorati

→ Write a Comment