Showing posts with label Teamness case studies. Show all posts
Showing posts with label Teamness case studies. Show all posts

Saturday, March 14, 2009

5 more tips and tricks with Teamness

Here are five more tips and tricks with Teamness for your delight. Please also checkout the previous five.

1. Project customizations

When the current opened project is one that you own, a link called "Settings" appear in the main menu that points you to a page where you may choose a logo for your project or set which tabs you would like to be displayed from Tasks, Milestones, Messages, Whiteboards, Files.

2. RSS feeds

In each of the following pages: Dashboard, Tasks, Milestones, Messages, Whiteboards and Files there is a RSS icon in the lower right side of the sidebar. You may use the link for that icon to feed it to any RSS aggregator of your preference. You may also subscribe to data from all the projects you're working on or your own created projects.

3. Email notifications

In the Subscriptions page you may check or uncheck the "Receive email notifications" check-box to switch between receiving or stopping email notifications for tasks, milestones, invitations or any other case.

4. Flag whiteboard version

You may flag as many versions of a whiteboard as you want. This is an easy way to remember that some are special. After you flag a version, a small sign will appear in the list of the versions for that specific one.

5. Export your data

In the Account page you are given the option to pack all the data from your projects as an XML file.

For performance reasons, the export can be performed only once a day. An email with download information will be sent to you as soon as the export is ready.

Wednesday, January 28, 2009

5 tips and tricks with Teamness

1. The startup project

If you're working on a few projects at a time, but one of them is the one that takes most of your time, you may choose one of your projects to be the startup project.

This means that each time you enter into your account, the current selected project from the projects list will be the active one. You can set the Startup project in the My details page.

2. Login through Google, Yahoo or both

You don't need to create a new account to be able to use Teamness. Just login with your Google or Yahoo account and you're all set. And if you already have an account created in Teamness, you may associate it with both your Google and Yahoo accounts and login with whichever you prefer.

3. Task titles

You may turn on and off the detailed list view of the Tasks page. When the detailed list view is disabled, only the first line of text from each task is displayed, like a title. This is especially useful when the tasks are quite verbosely described and you want to get an easier overview.



4. Print your project pages

You can print the information from each page with data from your projects, by using the print button available in the upper right corner of the page. For instance, this is how the View milestone page looks like:



5. Browser search bar for Teamness projects

Installing the search plugin allows easy searching your projects' data in Teamness directly from the browser search bar.

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.

Wednesday, December 31, 2008

Treat groups as sub-projects for a better structure

As mentioned in this post about organizing projects, a group may be considered as a project of its own, but still part of your existing project. Groups are a convenient way of organizing your data and using them as mini-projects is just one way of how you may use them to boost your productivity.

Let's take the example of a catering company who has a few regular customers, one being a company named Greedy Consumer (yeah, I know, clever name). The catering company takes care of their customers' orders using a project named "Food delivery".

Since they handle a lot of data for the Greedy Consumer, as recipes, messages and milestones for when the customer needs food delivered, they create a group named "Greedy Consumer" that holds all these objects.

It's easy to navigate inside this group, browsing only through data related to Greedy Consumer, because when a group is selected in one of the pages, the selection is persistent. For instance, if on the tasks page they select the group "Greedy Consumer", subsequently selecting the milestones page, it will show the milestones for this group.


This is just a hint on how you may use a feature in Teamness that I wanted to bring along with our sincere wishes of success with your projects in 2009, hopefully managed with Teamness.

Happy New Year!

Thursday, December 25, 2008

Teamness is open during Christmas

"Stores open on Christmas day" is one of the hottest search terms in Google trends these days.

Teamness is open for business during Christmas, pointing out another advantage of a SaaS tool: high availability, even during the holidays.


Image by Balakov



Christmas started nicely and warm for me, partly because I broke down the complex administrative tasks during this time as described here.

I wanted to write this short post during a break switching from home made sausages to Christmas cookies to remind you that you may use Teamness as your data bucket for these holidays period chores, following the Getting Things Done principles.

Here are some hints:
  • Create groups for different type of activities in your project, such as "Holiday meals".
  • Invite your family members in your projects and distribute the chores.
  • Put your notes in the messages area, inside the groups you created above.
  • Use milestones as reminders and attach tasks to them.
  • Upload files to keep them together in your GTD pool, arranged by groups.
  • Star objects that need your immediate attention.
You may access your data bucket from anywhere with an internet connection, without the need to synchronize it between computers. You can even print or export everything.

Merry Christmas, folks!

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 10, 2008

Focus on the outcome for success

One feature frequently requested on Teamness support was to display all the items assigned to a milestone. We also felt the need for an overview of all the tasks and messages that belong to a milestone, therefore the page View milestone was born.

Why was it needed?

First of all, let's think about what a milestone is. It is an objective that must be met during the development cycle. An objective is met by doing work, which is translated into tasks.


In Teamness it was possible to assign tasks and messages to a milestone, but there was no way to aggregate all these together.

How to use this feature?

One of the most powerful concepts of David Allen’s GTD system is outcome-based thinking, as Merlin Mann points out.

Setting the outcome like Merlin describes in terms of "I need to $FOO because I want to $BAR" gives you something you can use. It clearly shows the goal. But in order to avoid procrastination to settle, a listing of the steps to get you to this goal is required.

How about an example?

Christmas is coming soon. Santa Claus didn't reply to my letters, so I have to take care of the presents for my family this year. But doing Santa's job is a piece of cake with the use of the new View milestone page.

First, I'm setting the milestone, Merlin Mann style: I need to buy presents for my family members because I want them to feel the Christmas spirit.

Now that I have my goal set in clear terms, I need to build the list of steps. I create the following tasks and assign them to this milestone:
  • Make the budget for the presents
  • Find a nice blue shirt size 42 for dad, since I heard him saying he needs one
  • Decide if I buy my mother some piece of jewelry or an electronic photo frame
  • Look for websites where I can order that thing my girlfriend was dreaming about for months
Where does other stuff fall in?

While working towards completing the tasks, often you need to store various bits of information to help you in this journey toward the goal. Teamness allows assigning also messages to a milestone.

I used this feature to store various related information, like the followings:
  • I built a list of websites with Christmas gifts ideas.
  • I took some paragraphs from some blog posts about what others are considering buying for their family members.
  • Talking to my friends I asked what they are buying for their parents and then put all the notes down in a message named "Presents my friends are considering".
Here is how it looks like (click on the image for a bigger version):


We hope you'll find this feature useful and that it will considerably improve your workflow.

Monday, December 1, 2008

Overcome procrastination with Teamness

Regarding procrastination, I think there are two types of people: those who procrastinate and those who declare they don't.

Putting off things needlessly is a common thing most of us do. How many times did you postpone making an appointment for the dentist, even if you knew you're going to do it eventually? And how many times did you start working on different things, just to delay a burdensome task?

Image by celie

All of us have good business ideas. Most of the time we reject from the start and I think one of the reasons is that we procrastinate on thinking about a roadmap. When thinking about it, the path seems complicated and we tend to see mainly the obstacles.

In this post I'll present a simple way on how using Teamness and mind mapping one can get a better grip on how to pursue a new opportunity.

It all starts with an idea

For the sake of the example let's consider a guy Robert, which was on a holiday in France and bought a funny hat. At least he considered it to be funny, but he was asked a couple of times on the street where he got it from.

One day he asked himself what if he started to bring those hats from France and sell them. When he was about to let go, due to unanswered questions in his mind about the manufacturer, target market, shipping issues and so on, he makes a last effort and decides to give it try.

Turn the idea into a project

One of his friends recommends Teamness to Robert. "But I have no project to run, it's just an idea", was Robert's answer. That's exactly the point. Turn the idea into a project.

Robert creates a project in Teamness and calls it The funny hat. The purpose of the project is to investigate this business idea.

Brainstorming is the first step

He creates a new whiteboard in the project and starts writing all the things that comes into his mind regarding the process: existing products on the market, prices, target demographic, manufacturer, producing prices, shipping costs, storage and all other things that pop into his mind. Using mind mapping is really helpful in this process.

Time for tasks

Robert starts now to formulate questions based on the things he brainstormed about, like "What are the existing products on the market?". This question easily becomes a task: "Make a list with similar products on the market and their retail cost".

One by one, almost all of the other issues start to take the form of a task: "Call the manufacturer and ask for the price; try to get a discount for multiple purchases", "Identify areas for advertising for this kind of product and the target demographic", "Make a plan to microtest the product with PPC advertising" and so on.

Make the roadmap

Now Robert creates milestones. He makes one called "Target market analysis" and assigns the tasks related to his market to it. He sets this milestone to be due one week from now, based on some rough estimations on his free time.

As the project rolls on, information is collected in The funny hat project. Links, lists of prices, contacts, scans after brochures, screenshots made on some websites and so on are now all in one place and the idea turned into something more consistent. It's more clearly now what the good direction might be, based on real investigation rather than fuzzy assumptions.

Having a clear picture on how to continue, it's possible now for Robert to even delegate some of the tasks to a virtual assistant, which can help with some time consuming chores, understandably defined.

Wednesday, November 19, 2008

Teamness case study - wedding photography

Andris Zenta is a professional photographer from Latvia who specializes in wedding photography.

In the beginning, please introduce us to your work.

I've been working as professional photographer and illustrator for the last five years and recently I started to focus my interest into wedding photography. It's a very exciting field, but at the same time, exhausting. In any case, it brings me satisfaction both career wise, as well as from a financial perspective.


How did you find out about Teamness?

After shooting a couple of weddings by myself, I decided that I need two assistants to help me, one as a second shooter and one to take care of auxiliary tasks, like preparing the equipment or moving things around to set up scenes, allowing me to focus on taking the photos.

With more than one participant in this kind of project, there was need for a project collaboration tool. Since it was my first assignment with a team I wanted to try a free tool to see how it goes and I ran across Teamness by searching on the web for a free collaboration tool for teams.

I'm very satisfied on how it went and now I'm also seeing the benefits of using project management tool even if you work alone. It helps keeping you organized.


How did you use Teamness for your project?

I used Teamness so far for this wedding project I described, in which I had two assistants helping me.

Wedding photography is one of the most difficult tasks for a photographer. Everything must be very well planned, because you don't get a second chance to shoot the event. Preparation is then the key and Teamness helped us with being prepared.

A lot of details need to be settled prior to the event, like for instance dressing code. It doesn't seem like a photography task, but even if you're not part of the event, you need to blend in. This was written down in a whiteboard in Teamness which I named "General checklist".

The wedding had two parts: a first part in the church with shootings outside afterward in a nearby park and a second part taking place at the party, inside a location. We checked the weather for the day with shooting outdoors and stored the results in Teamness.

Prior to the wedding all three of us did some location scouting. We went to the established places and put down ideas for shots. We then discussed them in Teamness using messages and agreed on shot lists which we saved as whiteboards. I also prepared groups of tasks for my assistants and watched the activity on the dashboard.


What are the roles of every participant and how do you use Teamness for them?

I was doing the main shooting and one of my assistant was taking photos with a wide lens, covering more general aspects. We had a script prepared that list all the actions we needed and for each action I assigned tasks for my second assistant, like making sure to gather every member of the family at a certain time.

I established tasks for my assistants, first for the scouting session in which we simulated a real shooting and then for the wedding itself. The various stages were marked with milestones, for instance I had a set of tasks assigned for different talks with the couple: settings expectations regarding how many shots they want, what things to have covered and also the agreement based on which I charged them.

I made the equipment list for each bag, as different messages in Teamness and assigned tasks for the assistants to take care of each.


Are there any particular features that you value the most?

I liked that we were able to assign tasks to different persons and comment on them, so we agreed easily on every aspect. Building together lists of things to pack and do in whiteboards and seeing what everyone added was neat.


What would you improve in Teamness?

I would like a more flexible way of managing the items tied to a milestone. I would also like to see a richer editing feature for messages, in the same way as for whiteboards for instance. This was very helpful for us to accentuate on various equipment. I will stay with Teamness for my future projects, including a portfolio website that I'm preparing to build at the moment.


Thank you very much for your time.

Thank you.

Monday, October 6, 2008

Teamness case study -Training the students of the Faculty of Medicine

This post is the first one in a future series covering Teamness case studies with our users.

We plan to have these interviews with different people from various industries to get insights on how Teamness may be used to help with all kinds of projects.

Our first guest in these series is Cosmin Moldovan, Medical Doctor and General Surgery Resident at Witing University Hospital and Assistant to the General Surgery Department in Titu Maiorescu University, Faculty of Medicine, Bucharest.


To get started, please introduce us to your work.

My work has basically tree sides:
  • One is related to my practice as a general surgery resident at Witing University Hospital.
  • A more academic one, involving the training of the Students of the Faculty of Medicine and the preparation of the medical nurses.
  • Last but not least, I'm currently involved in a few governmental-funded research projects that involve tight collaboration between my University and other highly appreciated research centers in Romania.
We take care of students training from the 3rd year - Surgical Semiology, and from 4th and 5th year - General Surgery. At the end of the studies, we conduct the thesis of the students related to general surgery. We're using Teamness to collaborate with some of these students on their diploma theses.


Why did you choose Teamness as your collaboration platform?

Teamness is still a startup, but it offers everything we needed, and the current plan is free.

Another big advantage was the Romanian interface and the support that we can get in Romanian. Some of the persons involved in our projects are not very comfortable with English interfaces, so this came in very handy.

Regarding my work in research projects, it is vital to have a collaboration tool that you can rely on and Teamness came very handy with its on-line all-over high availability.


How many persons are in your projects and how many projects are you managing at this time?

Regarding the preparation of the thesis, we have a project created for each thesis. One or two students may collaborate on the same thesis. At the moment we're using Teamness for 8 such projects, involving 14 persons. In each of them, the participants are:
  • the coordinator, which is one of the two professors in charge
  • the assistant, which is me, in most of the cases
  • the author or the authors, which are the students
As for the scientific researches, I currently take part in 2 major projects, both involving three major research centers and universities, besides my own. In our university there are 4 persons assigned to each project and between 10 to 15 scientists from each other partner for each project.

Although our scientific ventures started back in 2006 and are due to December 2008, we have rapidly adopted Teamness as a major – but not unique – tool for our collaboration a few weeks after the service become publicly available.


What are the roles of every participant and how do you use Teamness for them?

The author gathers material, like images, short videos, quotations from various books and she/he stores these data usually as messages in Teamness. There are also translations made by the student from different specialized sources or texts that she/he writes, which we encourage to store as whiteboards, because this type of data is more subject to changes and it's easier to monitor who changed what and when.

The assistant reviews the data entered by the students and adds comments, makes suggestions or corrects some texts. Then tasks are added for what the student must focus next, which are tied to milestones. The assistant also sets tasks for the professor to see what is needed to be further reviewed, usually a subset of the data.

The coordinator supervises the activity using the dashboard. A neat thing here is that you can easily commute between seeing the activity for all the theses or only for one. The coordinator also checks student's drafts on certain stages and sets new tasks for the student, but also for the assistant.

Every month we all have a meeting in person, which we set via a milestone, with points to be discussed established as tasks tied to that milestone.


Are there any particular features that you value the most?

We like the ability to view all the activity on the dashboard, filter it by person and also view the activity across all the projects.

It's also nice that we can tie tasks to a milestone and see what we shall do until what time.

Being able to see the differences between two versions of a whiteboard is also valuable for our work. I also use RSS feeds to be informed about the activity.


What would you improve in Teamness?

Being at the beginning, there are a lot of things that can be improved or added, which I believe will be introduced in the future.

A thing that we would like to be included is granular access permissions, to be able to provide selective access to different areas of the projects for different members.

We are, however, very satisfied to be able to use a product without any setup, just based on email invitations.


Thank you very much for your time.

Thank you.