Showing posts with label Team collaboration. Show all posts
Showing posts with label Team collaboration. Show all posts

Friday, May 15, 2009

Learning from mistakes and test cases

Pawel was questioning the usefulness of test cases in one of his blog posts. I dislike useless documentation as much as any sane developer, but I see a strong reason for having test cases, besides outsourcing the tests, as one of the readers pointed out in the comments. My reason is regression testing.

Every time you test a new build of the software, you find bugs. Some are easy to reproduce and appear in daily usage scenarios. You want them fixed, otherwise they will get noticed by the users and most probably you don't want that.

In future builds, you would also like to stay free from the previously discovered bugs. Therefore you make notes about the context and the steps that led to the bug appearance. Surely, not every problem you find is worth keeping track of in a test case. A crash when accessing a web page with valid parameters doesn't usually need a test case, as you'll probably notice it anyway if it will come back.

At a certain point the build becomes stable and free of any obvious problems, which are easily accessible and reproducible. You find less bugs, but more subtle. The contexts in which they appear are not straightforward. Who would've thought to hit the Back and Forward buttons in a wizard 4 times in a row? Still, it's a malfunction and, if it doesn't happen only with Konqueror running on SuSE 6, you would probably want to fix it.

You make a note to check this bug in the next build as well. Throughout time, the list of notes is growing. You need to detail the context and the steps as much as needed, not necessarily as much as possible, because recalling all details in a few months doesn't really work.

Without noticing it, if you didn't want to acknowledge this from the beginning, you have a list of test cases.

In the future, if you think some of the test cases are not worth checking anymore, being obsolete or so, just delete them. Or better yet, mark them obsolete, to be able to revive them with some adjustments.

There is of course, automation, having the computer run a suite of tests for regression, instead of going through a list of test cases yourself. But this comes to show the same thing once again. These automatic tests are, in fact, test cases in a machine readable form.

Wednesday, April 8, 2009

The Catch-22 of functional specifications

Running away from writing functional specifications is a common thing. We prefer to talk about them. When someone joins the team, people from various areas of the project are asked to have a chat with the newcomer and provide her some insights.

However, these discussions have a tendency to repeat themselves in time and also change in a few ways, leading to chaos.

Writing functional specifications helps. Joel Spolsky shows how in a 4-part series, which may look daunting to read due to the length, but it's basically a 30 minutes lecture and it's fun and useful.

Why don't people write specifications, even for a small tool they built, that can be reused and that can clearly state what's going on? The invoked reason is always the same: no time!

This is the Catch-22 of functional specifications: people don't have time to write/maintain specifications, because they have to spend time explaining to their colleagues how things work. And they do this, because there are no up to date specifications.

Sunday, March 29, 2009

Recommended reading with Twitter

"Twitter is a waste of time", some of my friends are saying. "Why do I need to know what others are doing?"

I guess most of the reluctant guys take Twitter's incentive, "What are you doing?", too literally. Surely, this is not interesting in most of the cases. I couldn't care less when others wake up, if their coffee tastes good or if it's raining in London. Except if I'm going to London, of course. But in that case there are 100 websites to check the weather.

Twitter is a flexible platform. There are probably a ton of articles out there explaining the benefits of Twitter and the way one may use it. I guess one of Twitter's strong points resides in its mass usage. You can see what's hot. For instance, just search for "Earth hour" updates to get an idea.

A few days ago I was reading an article, probably this one, and I realized that amongst the things I read on the web, some of them I would like to keep track of, as in the case of the books. And I also want to share them.

I could use Delicious for this, as I do with all my bookmarks, but I wanted something like a stream of articles that are sent to more than my network of people on Delicious.

Twitter to the rescue.

However, I needed something more than just: "Hey, I found this nice piece of work - link", more specifically I wanted to be able to differentiate between other updates and the ones referring to articles.

Therefore I prefixed the update with the string #RR, as an acronym for Recommended Reading. The hash sign "#" is there to indicate some sort of a label for that update.

Ok, now I have the procedure in place, but how do I make these updates stand out from the crowd?

Chris Heilmann had a neat idea on how to dig through his series of updates on Twitter after certain ones. Here he describes how he used Yahoo Pipes to drill after tweets ending in a "§", the character he appends to each update he considers useful. Then he processed the last 5 tweets with Javascript to display them in a panel on his blog.

I shamelessly cloned Chris' pipe and changed it a bit to match my needs. I wanted a feed with the recommended reading updates, which is easy to get by changing a parameter in the pipe URL that tells the pipe what to render as result.

Here is the RSS feed with the recommended reading from Teamness. Please feel free to subscribe to it.

I also kept the Twitter id in the pipe configurable, so if you mark some of your updates in the same way, prefixed with #RR, you may use the same pipe by changing only the id below:

http://pipes.yahoo.com/pipes/pipe.run?_id=839250028c8c36570145554b0bcd190c&_render=rss&id=15095949

Sunday, March 8, 2009

The value of LinkedIn recommendations

Yesterday I found this blog post in which Jeff Atwood was questioning the value LinkedIn brings to its subscribers.
I've been a member of LinkedIn for almost two years now. I dutifully entered my credentials and kept them up to date. The only other interaction I've had with the service since then has been a continual stream of link requests. I'm selective about who I approve, limiting it to people I've only met in real life. And the net benefit of this selectivity? As far as I can tell, zilch. Nada. Nothing. I did get a cold call from a headhunter once based on my Linked In profile, but I don't consider that a benefit.

Has this service ever been useful to anyone? I'm telling you, Linked In is the digital equivalent of a chain letter. If you really want to contact a friend of a friend (of a friend), just pick up the phone or send an email. If the only way you can reach someone is through this nutty online social pyramid scheme, you don't deserve to be taken seriously. And I can guarantee that you won't be.

I'm not going to opt out of LinkedIn, as Jeff did. I still see a couple of benefits from it, like groups and QA, but I wonder about the value of recommendations.

What's the real value of a recommendation on LinkedIn?

Image by 1Sock


If you were to work with or hire someone, how much emphasis would you set on the recommendations that person has? Keep in mind that they are fully customizable, as the help states:
Yes, Recommendations can be revised, replaced or withdrawn by using the 'Make & Manage Recommendations' page.

Do you know anyone with a negative description in her or his profile? If the answer is no and I tend to believe nobody has one, then is everybody a truly skilled professional that provided only good value for every piece of work that she or he did? Or is this true only for people with any recommendations at all?

I have 61 connections, which might be considered a small number in today's networking situation. Out of these, I only gave one recommendation so far, for an ex-colleague that asked for it. He needed it for a new job he was trying to obtain. In any case, I would do it for every contact that asks me for one.

On the other hand, I got 3 recommendations to date. I felt good when I received these testimonials in my inbox, but my question is how valuable they are for an eventual business contact. I suppose that if I ask all my contact to give me recommendations, I'll get at least 20. So what?

Most of the recommendations I've seen on LinkedIn profiles sound like this:
[Name] is a very creative person, inspirational in the [field] industry, very focused on detail, great at deliverance and effective when is about results. Highly recommended.

I think a recommendation is actually valuable for the one writing it. If I was to pick someone to work with from LinkedIn, I would take these testimonials into account the other way around, by looking at the recommendations that person wrote for her or his contacts. Witty written ones, which break the above mentioned pattern, would be a plus in the evaluation.

Tuesday, February 24, 2009

The power of lists

This Sunday I drove to Oxelösund, about 100km south of Stockholm, to meet a friend. He works on an oil transporter ship, which berthed there for a couple of hours. We had some time to talk and at some point in our chat we got to discuss about work.

Loading a big ship with fuel oil can be regarded as a short term project. It's quite complex, comprising a couple of phases and things to be checked in each phase. He mentioned that they have strict procedures for everything.

This made me think a bit about lists. Most of us probably do build grocery lists, with an obvious purpose to not forget needed products. Like milk. I make a list most of the times I go to the grocery store, but when I don't, I usually forget something. Like dish washing detergent last time.

The loading procedure on my friend's ship has a list of things to do, which is written down. Everybody knows the items on it, but still, the list resides in a document. They check each point on the list as soon as it is completed, so in the end they know they followed the whole procedure religiously.

Making a list of steps in order to accomplish some work task might be helpful for you and for your colleagues as well. As the process evolves, the list is also likely to grow. New steps are added and why store them in our minds instead of some other place, from where they can easily and correctly be picked up later.

Some people don't want to reveal inner details of their work flow. They believe that keeping it secret will make them irreplaceable. But then, if you're irreplaceable, how can you advance?

When doing a task consisting of a couple of steps, consider making a list for each. It might be obvious for you at the moment, but it will help the others be productive if they need to get into that area. If it's not the case, are you sure you'll remember everything two months from now?

Thursday, February 5, 2009

New member's pocket guide to a virtual team

Two weeks ago, Sorin wrote a juicy post about welcoming a new member in a virtual team. There were a couple of times in the past when I was wearing the shoes of a newcomer in a virtual team and throughout time I learned from mistakes and developed some guidelines to keep me comfortable.

Image by 96dpi


Centralize data
I made a habit of keeping data centralized in a single location. It feels comfortable to know that you have a single place from where to start looking for your stuff. Every document, meeting minutes and conclusions from discussion on email or IM, things that I need to do for the projects and so on were stored in the central place. This doesn't eliminate the need to sometimes look for an old email, but at least it diminishes it.

Keep a worklog
At one point in the past I started to track my daily activity, by writing down as much as I considered relevant. Besides the things that I've been working on, the list also includes mentions of Skype or phone conversations with my colleagues. If you get paid by the hour, this is probably mandatory, but even if you don't, it pays off in time.

Stick to a strict working schedule

When I started working from home, it seemed cool to me to have a loose schedule. More like no schedule at all. But after a while I noticed that I actually didn't know when to stand up from the desk and call the day off. This started to affect my health and my ability to focus.

And there is another side effect of the schedule-free work style: your friends will consider you're always available and ask your help with different chores. If you don't commit to a time schedule, you'll end up doing other things when you should be focusing on work and you'll find yourself pushing working hours late into the night.

Schedule and timezones
Since the team is distributed geographically, the members could be on different timezones and it's good to know who is available and when. Worldclock and FoxClocks are two useful tools to see the current time of your colleagues.

Image by monkeyc.net


I used to convey upfront the time interval when I was going to be available. Even if I wasn't working in an office I still needed lunch breaks, so this was also included in the schedule.

Communicate often to keep yourself on track
Have a chat on IM each morning with the whole team, if possible, or only with your coordinator to say what you were working on, what do you intend to do that day and also ask what others are working on. Keep it short and concise!

Asynchronous interaction is your friend
Your colleagues are not in the office near you. Take advantage of this. You cannot be interrupted from your work flow and I suppose you don't want to. Rely heavily on email, collaboration tools, wikis and other non-interruptive mediums.

Invest in your workspace
If you're working from home and you just started your virtual work adventure, it's probably better to create a proper environment. Separating home from office is an advisable thing to do, even when the office is at home. So make it look like a nice office rather than a cozy place at home.

The Home Office Planner is a dainty book that comes to your help in transforming any space into a functional work area. You may also use IKEA 2008 Office planner, a desktop application for designing your office in a 3D view. The software let's you try various colors and also see the total cost.

Monday, February 2, 2009

Avoid the maintenance nightmare of duplications

In software development, duplicate code is considered a sacrilege. It leads to maintenance issues of the system, requiring more work to fix the same problem in a couple of places.

So then, it's pretty easy: just don't duplicate the code, right? It's basically as easy as saying don't eat bad food. Some people have the discipline to stick to healthy nutrients to an extent to which they find junk food disgusting, but the rest of use enjoy a juicy burger once in a while.

Image by Sam UL

As noted by Dave Thomas, one of the two authors of The Pragmatic Programmer:
If you have more than one way to express the same thing, at some point the two or three different representations will most likely fall out of step with each other.
To keep these representations up to date and therefore synchronized with each other, you'll find yourself stuck in the wasteful process of changing them in parallel, which I call the maintenance nightmare. And the nightmare reaches its climax when contradiction makes its way in.

The duplication plague extends beyond code. It reaches areas such as requirements or specifications as well.

It happened to me a couple of times to be directed to obsolete documents, when I started in a new team. These documents usually become obsolete because a colleague sends an email with a few notes, which become new requests upon subsequent replies.

Later on, someone else puts together a Word document that summarizes what has been discussed, which will probably get to be obsolete in a couple of weeks.

A solution that I found working was to establish a procedure of maintaining specifications and, more importantly, to stick to it. This may sound overblown, but it doesn't need to be: a simple guidance, presented as text is usually enough and also newcomers will benefit from it.

When a new email comes in with notes on how a process or a feature must be changed, make sure to update the single location where it was described so far and point everyone to it. Referencing that location in future discussions will habituate your co-workers into using the procedure you established together, eliminating the confusion induced by obsolete docs.

Friday, January 30, 2009

Eliminate assignment confusions

So you finished brainstorming over an idea and now it's time to get your hands dirty and do the work.

This moment is critical. A task doesn't necessarily mean the same thing for two different persons. Your idea about how to write the new contract may differ from John's, so if the task is not detailed enough, it might lead to the team pulling in different directions.

Image by Sean Rogers1


A solid approach would be to dissect the task down to manageable sub-tasks, that don't allow different interpretations.

Let's say you have to Promote the website for your business. It's a pretty complex task that can be interpreted in many ways.

But if you slice it into more manageable things to do, the bewilderment fades away:
  • Find 10 website directories and enter the website under the proper categories.
  • Write a press release which includes the 5 most useful services the company provides.
  • Submit the press release to 5 online agencies.
  • Write an whitepaper about a solution your company/product is offering.
  • Set up a Google AdWords account and start a campaign.
Besides clarifying the work to be done, other benefits of breaking down a complex task include:
  • You get a better estimation of the duration of the task.
  • The progress gets easier to follow. In my opinion, this approach is more useful than using flimsy percentages which usually get out of control.
  • You have a list of actionable things to do, instead of a complex unclear assignment.

Monday, January 26, 2009

Brainstorming remotely

Today I started a short conversation with Pawel Brodzinski, about how teams respond to working exclusively remote. By the way, his blog, called Software Project Management, is a great resource of posts about working with teams and managing the process of software development, so make sure you subscribe to it.

Pawel was talking about the lessons learned from a startup product called Overto, which was closed some time ago. One of the things he mentioned was the value of working in the same place and the way his team started to feel the negative effects of being separated.

Image by timabbott


Since I believe in the remote proficiency of virtual teams, I had a different opinion. I think that after the preliminary discussions around the fresh idea of the product, collaborating in writing instead of ad-hoc meetings may bring great effectiveness into the product.

Written communication versus spoken brainstorming

I mentioned the following arguments for communicating over writing mediums, like email, as opposed to verbal meetings:
  • On email it's more natural to keep the discussion focused on an aspect. Talking makes this a bit chaotic.
  • It's easier to follow a point of view, when you have it written on the screen, maybe with additional links to external resources.
  • When you need to write, you focus more on the points you'd like to add to the discussion. Talking is faster, so it might lead to loosing the focus.
  • Everything that's discussed gets logged, so you avoid the post-meeting confusion over some pieces of conversation or forgotten parts.
  • You're undisturbed in your own mind-mapping flow process and you don't disturb the others.
Brainstorming over emails might be a bit sluggish from the point of view of generating ideas based on ideas being generated by the others, but in my opinion it's better in refining an idea before exposing it.

Let ideas flow, then examine the results

It's pretty common that once an idea is out, it's exposed to being examined. This leads to context switching and instead of focusing on building a list of things to discuss about, you'll find yourself analyzing ideas.

For instance, when you discuss holiday destinations with your spouse, it's probably the case that you find a place, discuss about it, then find another, comment on it and so on.

The drawbacks of this approach are presented more explicitly in the book The Myth of Multitasking. The book includes a demonstration that switching back and forth between two different tasks, makes them take more time than doing them sequentially.

Image by h.koppdelaney

The above example is a bit extreme, since it involves the spouse. Don't do it at home unsupervised. But in my opinion, the same thing applies to teams and brainstorming. It's nothing wrong with getting together for a drink/lunch and discuss about a new product or feature, but I find writing more efficient.

Use mind-mapping, build a list of things that you think are suited, and then pass it on. If the others are doing the same, undisturbed, your team ends up with a more productive flow of ideas and better yet, you have everything written down.

Experiment and stick to what works for you

I'm not trying to say that this model is supposed to work for everyone. We are a team of two people, me and Sorin. It's been like this not only for the time we've been working on Teamness, but since 2005 when we started our company. We used to work from home on different projects for some clients and we always collaborated remotely. This is basically the reason for building Teamness in the first place.

In the beginning we were talking on Skype about clients, implementation details, decisions and so on. We used to have long conversations and sometimes we didn't remember everything that was discussed. We still have conversations, but when we talk about new features or design decisions, we use Teamness. We write the proposal in a message and then comment on it. This keeps it focused. We also use email from time to time, but what I want to stress upon here is that we're trying to keep the verbal communication related to our projects to a minimum, since it didn't prove efficient for us.

Please also note that I'm not trying to express that social interaction is bad, like having lunch with your colleagues or coffee breaks discussions. But when your product has 1000 features, writing things down becomes the key ingredient for a solid collaboration.

Thursday, January 22, 2009

How to welcome a new member in a virtual team

Teams grow and change. New members arrive and they need to be accustomed to the culture of the organization, the project and the process.

This might be a frustrating experience both for the newcomer and for the team. Virtual environment makes it even worse. Lunch breaks with the colleagues to ease the process are not possible and there is no watercooler for chitchat.

Image by etringita


In an office environment, it's a common practice to have a couple of meetings in order to introduce the new person to the project she's supposed to work or into the organization. But in a virtual environment, it's a bit harder to put the focus on meetings. Web conferences can be done, but they basically help only with the introduction, not with the integration.

In my opinion, a virtual organization should accomplish at least the following prerequisites in order to make the new one productive as soon as possible.

Make the newcomer feel part of the team

That's easier with a physical presence: an actual office, going out for lunch with colleagues, t-shirts with the logo etc. In an online environment, if the organization has a blog make an author account for the new guy and encourage she/him to write a post to describe his feelings regarding the new environment.

Assign a meaningful role for the newcomer

She or he might feel overwhelmed with the information needed to be absorbed.

The tricky part is that you cannot afford to have one of the team members absorbing all the information the other members have. In theory, it's a never ending process: by the time she would have the knowledge an existing member had, that one would be far ahead. And after all, the knowledge one team member has shouldn't completely overlap with another. Everyone should bring something new.

The solution is to encourage the new one to dive into work and try to complete an easy task. The task should be a real one, because otherwise the motivation to do it will be diminished. This way you also bring out the practical aspects of the guy, which is probably why you wanted him in the team in the first place.

Have all the tools configured for the new account

Don't let the guy wait around a couple of days or weeks because he doesn't have access to the tools you're using with the others. The new account must be easily created with the appropriate rights for the newcomer in every application you're using: blog, wiki, tasks tool etc.

Image by tochis


Document your decisions and procedures

This is an ongoing process, from which everyone in the team benefit, but it will prove itself useful for a new member as well.

There would still be a lot of questions and interruptions for you and your team to help the new one get acquainted, but a lot less than without a proper documentation. And the documentation shouldn't be built just before a new one comes, but throughout the life of the project/organization.

This is so easy and straightforward to do, but still disregarded by many: write everything down. If you need to explain a procedure or a feature to one of the colleagues, after you discuss on it go and write it down. Don't use applications designed for something else, like Word or Visio or other UML or word processor, but some simple text wiki/message environment, which allows for easy editing afterward and it's easy to share.

Procedures usually change in time, so the more difficult you make it to update them, by drawing schemas and format text, the less likely that you'll do it, rendering them obsolete.

Provide feedback often

Don't keep the newcomer in suspense. Let him know often where to pay attention, what to improve in the process and ask him questions. Leaving the guy one week to read documentation is boring and will make him loose focus.

Keep an up-to-date list with the existing members and their roles

The new guy will have questions. A lot of them. Don't allow for his questions to bounce around from one guy to another, until he finds the proper person to ask. Maintaining a web page with who's in the team and what everyone is working on might be a time saver.

Monday, January 19, 2009

Social aspects of productive virtual teams

When we think about efficiency in a virtual team, we often relate this to being effective in a practical manner, like optimizing our workflow in the online environment or having the right tools to interact with our colleagues.

But there is also the social aspect of such a team.

Image by Allis0n J


Even if the people are not together in the same office, social interactions still take place. In an article called Working Together … When Apart, the author gathered what she calls ten golden rules for making virtual teams more productive.

The list is based on a research that surveyed more than 1500 virtual-team members and leaders from 55 teams across Europe and U.S. and it also covers social facets, as selecting team members based on their relationships or encouraging frequent communication.

These are the 10 hints:

1. Invest in an online resource where members can learn quickly about one another.
2. Choose a few team members who already know each other.
3. Identify "boundary spanners" and ensure that they make up at least 15% of the team.
4. Cultivate boundary spanners as a regular part of companywide practices and processes.
5. Break the team’s work up into modules so that progress in one location is not overly dependent on progress in another.
6. Create an online site where a team can collaborate, exchange ideas and inspire one another.
7. Encourage frequent communication. But don’t try to force social gatherings.
8. Assign only tasks that are challenging and interesting.
9. Ensure the task is meaningful to the team and the company.
10. When building a virtual team, solicit volunteers as much as possible.

In the article you'll also find examples about how virtual teams in well-known companies employed the hints.

The rules cannot be applied in every context. Not all the tasks can be challenging and interesting, so point 8 has to remain unsatisfied from time to time. But the list remains relevant for both small and large teams.

Friday, January 16, 2009

Managing project collaboration

I'm sometimes asked if Teamness is able to solve various specific project management issues, like financial resources dependencies or risk management.

Not really. Teamness is a project collaboration tool. It was born with the intent to help people gather their projects data in a centralized place, from where they would be able to share it with their colleagues.

Easy online project collaboration for teams is our tagline. Saying that I'm currently managing to collaborate on my projects using Teamness doesn't necessarily mean that Teamness is acting like a project management tool, in a way a CEO would see it.

Image by David


We're not building Teamness exclusively for people in suits, but also for the aspiring freelancer or members of a family who work together on home projects. You don't need a MBA to use it, but merely a Google or Yahoo account.

We want Teamness to be flexible enough to accommodate any collaborative task you're taking. After all, real work is done by real people, which in my opinion get motivated by awarding goals, not well connected Gantt charts.

Teamness has been working fine for our purpose so far. By using it, we see different aspects that need to be improved and we're adding them in the task list and we're open to suggestions and feedback.

However, Teamness was not designed with the intent to help a project manager manage her or his team, but to help a team manage their projects together.

Wednesday, January 14, 2009

Podcasts to help with your work

If you feel like getting away from the news or if you're trying to find new ways to keep your headphones on most of the time, here's a post about how you may fill your mp3 player with podcasts and get hints while you prepare breakfast.

One podcast you may add to your list is this one, which covers some topics on virtual teams, like challenges, social aspects and trends. I don't share their affinity with instant messaging tools used for work interaction.

Make sure you also check and subscribe to IT Conversations, a network with great talks on various topics, from education and history to investments and social networks.

Friday, January 9, 2009

Planning a project

In a virtual team, a certain degree of coordination is needed to get the work done. This depends on the team size, which is usually determined by the project magnitude.

But even for personal projects, you still have a plan in mind before you begin working. In my opinion, a project plan, big or small, has to incorporate the following elements:
  • Scope
  • Requirements
  • Tasks
  • Schedules
  • Cost estimates
All of them are usually subject to change throughout the project lifespan, but you still have to take them into account when starting a project.

Image by anesterik


Scope
The scope is a high-level vision on the project. It provides a justification for the effort and describes the project by including the following:
  • Goals - what is the project supposed to achieve?
  • Major milestones - when will the goals be accomplished?
Requirements
The requirements are your project's necessities, which will include at least the following:
  • People - your team, which may vary along the way.
  • Tools - Internet access, email, collaboration platform, skype and/or any other supplies of any kind.
Tasks
You may start with a set of tasks for each person involved. Each task may have a brief or a long description, according to the intended audience.

Teamness has a nifty way of presenting tasks, either showing the whole description or only the first line, considered as a brief or title. This is per account, so team members familiar with the actions to be performed may look only after the title, while others may choose to see the details.

Schedules
Once a task list is in place, a schedule might be started to take shape through milestones. The difficult part is knowing how much a task will take, but this doesn't mean you cannot have an overview. You can modify the due dates later, also pushing the subsequent milestones.

A virtual team would probably be distributed around the globe, thus celebrating different holidays. Earth calendar is a daybook of holidays and celebrations around the world, which can help you know which members of your team would be preparing a celebration dinner when you're getting ready for a new deadline.

Cost estimate
Once you know how long your project would take, the size of the team and their availability and which tools you need, you can create an initial rough cost estimate. This is based on the information from high-level scope, along with the tasks listed so far, but it will be refined as the work progresses by eliminating the "black box" evaluations.

Thursday, January 8, 2009

Maintaining agility with Teamness

Not being tied to a particular process, such as Scrum, might be a flexibility advantage to a team looking to follow its own process of development.

Teamness is a loose structure web tool that allows a small lightweight agile team to use its own custom project work approach.

Image by Scientific deliriums


Here is a set of hints on how to combine Tasks, Messages and Milestones within Teamness to manage your projects in an agile way in 2009 and beyond.

1. Use Messages for briefs and support requests

A brief for functionality or a support ticket can be a Message entered into Teamness within the appropriate group. Once the brief is processed or completed, this might be marked by moving the Message into a different group.


2. Use Milestones to create project goals and timings

Generally the project manager will create the Milestone after discussing with the team about time and availability, in regard to customer priorities.

Milestones are the glue which bind together details (Messages) and work (Tasks). Once you create a Milestone for a list of tasks, you can now bind the Messages to it.

Selecting a Milestone gives visibility into both the customer and team facing aspects.


3. Group Tasks under Milestones

Each Milestone can have tasks assigned to it. This task list should be set up to allow you to track time against it.

By having a single goal with track-able time you can then start making the actual work declared as Tasks. This allows an individual or mini-team to manage their own specific goals without making the high level project plan dirty.

This approach of using task lists also means that you can track your progress against a single Milestone which means you don't have to move all your tasks from week to week.

Milestones can be set up really fast and yet they can be moved if other demands come in, without having to micromanage a list of items which cannot be done in time anymore.

You also have the possibility to shift in time the subsequent milestones of the one you intend to move.

Friday, December 19, 2008

Using Teamness to sell flower pots

A friend of mine wants to start a business selling flower pots and she asked me how Teamness may be of help.

I came up with a few questions to clarify her needs and I suggested some ways on how to deal with them in Teamness.

Image by cwalker71

How do you intend to sell the pots, online or in classical shops?

I would first like to start on the web, with an online store. Then I intend to collaborate with existing shops, both virtual and "physical", like flower shops, design houses.

The web site will evolve in a project of its own, having a high activity in the requirements phase, development and testing and at a slower pace afterwards, in the maintenance period. So I suggested separating its administration in a separate project called Flower pots website.

The rest of procedures of the startup can be put in a separate project called Flower pots. The name can be changed at any time, but we don't append startup or something similar, since it's highly probable that we'll use this project to track the whole business life span afterward.


What are the initial issues for this business?
  • Perform an analysis of the competition and try to identify niches, finding missing details, like alternative materials for the pots.
  • Build the requirements for a basic e-commerce website. Once having the requirements, I want to contact a few companies that could help with the whole infrastructure (hosting, server, web application etc) so I can move on to the next step.
  • Discuss with potential partners. I think it's easier to not be alone in this journey.
  • Find storage space for the pots and establish initial stock of products.
  • Contact suppliers and discuss the conditions.
  • Contact delivery companies and discuss the conditions.
  • Calculate the initial amount to be invested.
  • Micro-test the product using Google AdWords.
  • Buy ads in related web and paper magazines, like gardening or blogs about flowers.
Every point in this list is a mini-project of its own, therefore I suggested defining milestones for each.

Breaking down these points into sub-tasks offers a clear vision on the roadmap for each of them.

When she has to Perform an analysis of the competition, she needs to know which competitors to follow, hence the first task: Search on Internet and in the gardening magazines and identify 5 top flower pots resellers.

Suddenly, this rather ambiguous job of analyzing the competition has a starting point. List the type of pots they're selling (material, size, model etc) and the prices, could be the subsequent task.

The result of the analysis above goes into separate messages: List of competitors, Possible niches for flower pots, which also lead to further steps in terms of milestone, like Contact 3 flower shops as a client and ask them why they're not selling a certain type of pot.


Who's going to be involved in this and what are the roles?

For starters, me, then my partner and afterward, an accountant who will take care of the legal finance issues.


My partner will take care of the administrative issues, like finding storage space, dealing with the company building the website and the delivery company.

I will be discussing and making the contracts with the suppliers; I'll design the first set of pots and take care of the advertisements. I also intend to outsource the whole process behind the website, including the hosting and the setup.

The partner is not known at this time, so he/she will get an invitation in both the website project and the administrative one at a later time.

The accountant can be welcome in a separate project, dealing with financial data, since it's not necessary to be involved in all aspects of the business, like brainstorming about the types of pots.

Creating more granular projects for different types of activities offers a clearer way of administrating the work done. People from the company involved in the website work don't need to know the data the accountant works with, so separating their work is more helpful in getting a good grasp on each part.

Also, once a project is completed, it can be archived, leaving more room for active ones.

Monday, December 15, 2008

Break down complex tasks with milestones

Is there any task in your project that seems un-doable? A task that causes you repugnance and makes you pass over it all the time when considering your next action? As Merlin instructs, break it down.

Sometimes what we think to be a task is actually hiding a sequence of things that need to be done. Drilling down and revealing this sequence is an incentive to get going with the work.

With Teamness, this can be easily achieved with a milestone. Make a milestone out of that task and tie a list of sub-tasks to it. Even more, by using messages you can store more information and brainstorm with your colleagues.

Let's consider an example of a couple, John and Jenny, who decided to throw a Christmas party for their family. A part of this project is the task of preparing the food.

They made a task called "Think about the food" which got assigned to John, since he's a better cook, about 2 weeks ago when they announced they're going to host the party this year.

But the task didn't seem appealing to him. Only the thought that he has to think about preparing food for around 12 persons made John scan quickly over this entry in the tasks list.

Image by Aim and shoot!


The time was getting short, so John had to stop and evaluate what he needs to do. He realized that the action of thinking about the food, as was first noted in the task, is in fact a list of actions.

He made a milestone called "Planning the meal" and assigned it to both him and Jenny. The due date for the milestone: December 23. By then, they have to have everything sorted out.

"Make the list of guests", "List their culinary preferences", "Create a list of 6 dishes to prepare", "For each dish build a list of ingredients", "Make a cost estimate for the groceries", "Prepare a list of drinks", "Select wines according to the dishes" were all tasks for "Planning the meal". John distributed them to him and to Jenny and tied every one of them to the milestone he just created.

Image by abbyladybug


He spent some time on the web to find a few pages with hints for the above tasks and put them in separate messages: "Blog posts with Christmas dinner ideas", "Recipes for the Christmas", "Red wines" and "Christmas deserts". He also attached the messages to the milestone.

By creating a small mini-project out of the tedious task from the beginning, John made it easy to grasp the actions needed to complete this chore.

Creating a milestone offers a couple of productivity benefits:
  • tying a list of sub-tasks to the milestone you actually build a list of actionable things to do
  • using messages you can keep a lot of information and brainstorm on it with your colleagues
  • having a due date for the big task works as an incentive to do it

Friday, December 12, 2008

Organizing projects

What is the structure and behavior of your organization? was the first in a series of 5 questions to ask yourself when evaluating project management tools, a post in which Paul mentioned the distinction between project-driven and functional-driven organizations.

The structure of an organization strongly influences the way its projects are organized and in this post I'm writing about some options you have when doing this structuring.

Image by Thomas Hawk

Generic or specific projects

The project-driven organization may be more inclined toward creating more generic products, while the functional-drive one may opt for more specific ones.

Some examples of generic projects:
  • Product development
  • Website
  • Wedding photo assignments
Examples of specific projects:
  • Search engine optimization for blog
  • Photo assignment - Clara and Brad's wedding
  • Library lawsuit
In any case, depending on the current needs, it's a good practice to try both specific and generic projects to see which works better in a certain situation.

Naming the projects

If you deal with multiple projects or if you decided for a more granular approach, the names of the projects must follow some rule to allow easy scanning and referral.

One way of doing this could be to name a project as following: the initials of the company for whom the project is done, the year when it was started, a numeric index and description:
  • IMA - 08 - 012 -Web pages optimization
  • KD - 07 - 010 - Staff management
This naming convention is also useful if you put labels with the same identifier for written documents, like invoices. This way it becomes more easily to find a certain paper a few years after the project completion.

The granularity of the projects

The complexity and the level of activity in a project is also a factor on how it should be organized. Here are some variants you may take into account with Teamness:

Granular projects - a small project might be created for a part of your work. For instance if you want to launch a business for selling t-shirts, you may divide this big activity in 3 smaller ones: a project for the administrative process of the business, a project for your website and one for an eventual blog.

Groups in a single project - if you feel the granularity described above is too intricate for your activity, then you may create a single project in which you create groups for the processes: a group for sales, one for marketing, one for the website and so on.

Mini-projects with milestones - a milestone with tasks and messages tied to it might be regarded as a mini-project or, if you prefer, a sub-project. Going back to the blog example, it can be seen as a sequence of milestones for posting activities, with tasks tied to each representing the ideas for posts and messages containing drafts.

Projects durations

Some projects are perpetual, like the maintenance of a product, while others have a limited time span.

In Teamness it is possible to archive a project and you may want to do this with a project that doesn't have any activity anymore, due to its termination or if it's in a paused state. Archiving a project will free up another spot for a new project within the current plan limits.

Wednesday, December 3, 2008

10 practices to be efficient in a virtual team

Following Sorin's post about working in a virtual team, I decided to write about 10 practices that in my opinion improve a lot the efficiency of a geographically dispersed team, which is using the online medium for business.

Image by SpoiltCat

1. Be strict with email
Don't eliminate email but be disciplined in using it. Also, you don't need separate accounts for personal and business use, but make use of filtering. Keep all the conversations for later search.

2. Use a project collaboration tool
A project collaboration tool must help you keep all your stuff together: tasks, milestones, notes, messages, documents. Sometimes it's easy to let go of this idea, with excuses ranging from: "but what we're doing is not actually a project" or "we use email and we're fine". Email cannot replace properly the role of milestones or tasks, for instance.

3. Write everything down
There isn't a straightforward replacement for the water cooler in a real office. But in a way, this might be an advantage. It happened to me a lot of times to discuss on ideas with my colleagues, only to notice later that we remember less than half of the ramifications our conversation took.

4. Brainstorm and expose
Save any idea that comes to your mind and share it. Let your colleagues "play" with your notes. In turn, find different approaches or fine tune your team mates' proposals. A thing to be careful about here is to avoid going too deep in one direction, since this can be the recipe for getting nothing done.

5. Keep documents in one place
Resist the temptation to send documents as attachments to emails, but upload them in your collaboration application. You don't need to build a hierarchy for the files, just use the search approach.

6. Turn limitations into advantages
In a real office, if someone has a question for a co-worker usually goes to her desk to ask. This is bad, since it creates interruptions and breaks the flow. When working in a virtual team, don't try to mimic the same behavior. If the colleague is not online on IM, don't wait for her but leave a comprehensive message, preferably in the collaboration tool.

If you have a question don't just ask it and wait for an answer, as this may lead to very long conversations. Instead provide all the options you thought about as possible answers, specifying why you like or dislike each of them. This diminishes the time spent on an issue, thus increasing efficiency.

7. Set a working schedule
Everything is set up regarding the way you interact with the colleagues and you're enjoying the flexibility of your own schedule to do the work. But in time, this can get out of control if you don't establish a working schedule for yourself. Spreading the working hours throughout the whole day may affect your personal life and you'll end up "working" all the time, not knowing when it's enough for a day.

Having a schedule also helps the other members of the team, since they would have more accurate expectations on when you're going to do various tasks.

8. Set iteration milestones
Working in iterations is a good practice to have a clear overview of what needs to be done next. It also helps to see if the deliverables were met. Weekly iterations offer a convenient time frame, but depending on your team this may be reduced or extended. However, extending them too much would be like not having them at all.

9. Stick with a given workflow
If you started to use a collaboration tool, keep everything in there. Don't scatter discussion about features of the product in emails, but use messages in the tool. Don't ask for things on email or IM, but set tasks.

10. Get to know your colleagues
If it's possible, meet your team mates personally, go out for a drink or make weekend trips. Getting a glimpse into their personal life and also exposing some of yours helps with the work. If that's not possible, try to connect with them on social networking websites. Find out their hobbies, maybe they match yours, and exchange thoughts about them.

I would not state that this list is exhaustive, but I think it covers 10 important aspects that lead to easier communication and a better workflow in a virtual team. Almost all of the points rely strongly on self discipline, but once it's achieved, it's easier to keep going.

Friday, November 14, 2008

The project triangle

I'm reading "Dreaming in code", a book trying to find the answer for this question: why is software so hard? It's probably fun to read for anyone who ever participated in creation of any type of software as it follows a project doomed to endlessly spin without getting close to the initial vision.

One paradigm that drew my attention lately is the Project triangle, mentioned in the chapter "Managing dogs and geeks". The project triangle is a painful formula coined in the software development field, which states that given the options of Fast, Good and Cheap, you have to pick two of them to build a system.

With the recent explosion of web 2.0 tools, I tend to think that the solution for the problem was nailed down. In my opinion most of the small companies releasing services on the web are first getting comfortable around the Fast and Cheap options, then releasing the product and after that iterating over Good.

Leaving Good at the end doesn't mean that the initial state of the product is unreliable. It means that the product is refined in time, following the feedback received from initial users to pump up the Good side of the triangle. Web 2.0 redefined the term Good from the triangle.

If you didn't read the book, I recommend it. Joel Spolsky wrote a review about it here.