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.

Wednesday, November 12, 2008

Twitter pals

We are big fans of Twitter and with its growing popularity we believe it's a very good tool to make contacts. We recently started using Twitter to promote Teamness through it and we try to stay focused on this purpose, without being obtrusive. At the same time we watch what other people are doing and writing about.

To make our Twitter life easier, we're using a couple of related tools and in this post I'm going to list them with a short description:

Twitter Search
We mentioned Twitter Search already in this post, writing about the way we use it to stay up to date with Teamness being mentioned in the tweets.



Tweetburner
When you include an URL into an update, Twitter converts it to a short one using TinyUrl. Tweetburner does the same thing, only that it tracks the links your URL receives. This way you would know how many people clicked on the URLs in your messages.



FriendOrFollow
With FriendOrFollow you may easily see who you're following that's not following you back and who's following you that you're not following back. You may also see your mutual follow contacts. It's a fast way to follow back at interesting people who are following you already.



Tweetscan
Tweet Scan searches Twitter and other micro blogging services and delivers reports on email or RSS.



Twittercounter
This tool shows you how popular you are on Twitter. You'll get a nice graph with the daily status of your followers, so you'll see how many more are following you day after day. Or, sadly, how many stopped following you.



Yoono
Yoono is a browser add-on that aggregates social networking information and keeps it in one place. It comes in very handy especially if you're active on a few social networks and you want to handle all of them from one place.

No matter what are the tools used, make sure you use Twitter for business the right way. As written in the post, it's more valuable to actually interact with people than hastily promoting your products.

Here is another list of Twitter related services and in this post you'll find a presentation of five ways to connect to people on Twitter.

Monday, November 10, 2008

Working in a virtual team

Managing the work on Teamness is done entirely virtual using basically two environments: Teamness for all kind of data and Gmail. In this post I write a few thoughts about being part of a virtual team.

Image by Zed.Cat

Virtual team allows for mobility, but mobility doesn't mean absence. You need to work on your virtual presence and in today's world there are plenty of online tools to ease this process. These solutions are moving teams beyond phone and email, giving more and more space to other means of communication.

Stay up to date with what your team work. Micro blogging platforms like Twitter increased the frequency of achieving this. Posting five times per day about work related activities may replace the little chit-chat on the corridors in a real office. Everyone in the team may participate to these virtual discussions and you can even organize virtual coffee breaks while actually drinking coffee.

Looking at the results rather than activity is the efficient way of managing a project and the virtual world makes this task even easier. The list of completed tasks shows clearly if you were just busy with unimportant issues or you were focusing on being productive.

Don't use IM for business. IM instigates to chat and to endless discussions around the same subject without drawing conclusions. This is not what you need to get the job done. However, if you started twitting, make sure you're not transforming this into a new IM environment.

Eliminate meetings with a project collaboration tool. In my opinion, the only good thing about meetings is brainstorming. Use messages for that. Establish deadlines with milestones and create tasks for things that need to be done. Discuss those using comments, to clarify all the aspects. A summary of the work done can be obtained from the dashboard.

Connect personally with your colleagues. As Chris Nagele points out in this post: "nothing helps a team gel more than learning about each others personal lives". But it's not very difficult anymore to get connected with your colleagues. Social networking websites help sharing profiles about team members. Connecting with your colleagues on Flickr and looking through their photostreams you'll find out things you would otherwise talk about near the water cooler in the office.

Be consistent in using these tools. Doing this builds trust in time and eases the interaction with the team. Each member of the team would know what to expect from the others.

If you're working remotely or if part of a virtual team, you might want to also checkout FreelanceSwitch. If you're travelling a lot, Portableapps has a large collection of software that works on any "USB flash drive, iPod, memory card, portable hard drive or other portable device".

Wednesday, November 5, 2008

5 questions to ask yourself when evaluating project management tools

Students participate in online groups to chat and share information. Small companies use emails for communication and network drives for storing documents. Non-profit organization may rely on a free online solution. Software departments could keep the schedule in an Excel file. Some individuals use notebooks and pens to put down appointments in a paper agenda or type reminder items in an online or desktop solution on the computer.

The name and the complexity of the tools used vary with the type of organization and the activity performed. Every organization, from big companies to individuals, uses a mechanism for project management, even if they don't call it like this.

Image by El Fotopakismo

In this post I will try to identify a few preliminary questions that may be asked to asses the needs for an online type of project management solution. It is not meant to be a complete and exhausted list of questions, but more of a guide for choosing a solution that will best suit the needs.

1. What is the structure and behavior of your organization?

Project-driven organizations have different internal processes than functional-driven ones.

Examples of project-driven organizations are: a construction company who builds wooden houses, a group of students working on a class assignment or even a wedding photographer doing assignments.

A functional-driven organization is usually a service or information company, like a small family hotel or a department in a bank working with processing checks. Such an organization may need to define either small multiple projects, which can be archived when becoming inactive or define fewer ongoing ones for each type of activity.

2. What is the complexity of your projects?

The number of people involved and the estimated activity must be taken into account. A project generating a lot of data, with a high posting frequency needs a fast solution on the web and options to filter and group the data for easier retrieval. Searching is a must, since it's easier to archive and look for, instead of spending time classifying the data.

3. What is the life expectancy of a project?

Some projects don't have a deadline, like an on-going activity for a functional-driven organization. They may require task grouping under milestones, though. A project with a long life span faces the challenge of getting old data out of the way, but being able to retrieve it at any times.


Image by lumaxart



4. Are the projects internal?

If everything is public for everyone in the project, a solution with complicated privacy policies is not needed. But if you need your clients to have a peek once in a while, you probably don't want to expose everything from under the hood.

5. Are you already using any software for disciplines related to your activity?

If there is already an established procedure for certain disciplines involved in the project, like requirements management or issue tracking, the transition to the new solution must be as smooth as possible. The learning curve for your team should be as easy to climb as possible. Trying to keep the same type of workflow can save a lot of time.


This list doesn't cover many aspects related to choosing a solution, for instance there is nothing about security. I wanted to keep the list focused on the workflow of the team.

Simple tools like online todo lists, text or Excel files may be more efficient than a complex solution, so it's important to identify the requirements prior to deciding for a given solution.

Sunday, November 2, 2008

Blogging for a startup

A lot of blogging resources recommend having a blog for your business. A blog can be useful for various reasons, the most important one being that you may promote your product.

I believe that for promoting the product, the content of the blog must be interesting enough for people which are not familiar with the product to come and read the posts. Then, they find out about the product and use it, fulfilling the mission of the blog and not the other way around, having the product sending readers to the blog.

Image by El Fotopakismo

Some of the general reasons mentioned for having a blog as a business include:
  • Announcing new features. This is good, but then your readers would be the users of your product. Who else is going to read a list of upcoming new stuff you worked a lot upon, other than the already existing users? In Teamness, we made a special page called News, where we're adding information about new features. There is also a RSS feed provided for this News page. This way, we spare the users who are only interested in the product to spend time going through our blog posts.
  • Frequently asked questions about the product. Why spread them around posts in a blog, when you can display all of them with a searchable feature in your website? In Teamness we gathered them all under the Help page. We also implemented a mechanism to offer contextual help, by sending the user directly to the questions in Help referring to the page she/he started from.
  • What are you working on. This is also related to announcing new features. It might be interesting only for existing users.
  • A mix of the above. Not such a good idea, in my opinion. As problogger describes it, writing about multiple topics on a blog makes users "became disillusioned with the blog". People wanting to know if a new feature is available will become annoyed by other types of posts.
Then, what's left to write about?

Many of the advices found on the web regarding blogging for business omit the fact that as a startup, you would want to maintain a blog in order to get users for your product. Therefore, we think that the blog has to become attractive, independently of the product.

We are continuously trying to find subjects to write about in order to keep this blog interesting. We found two interesting directions:

Writing about Teamness as a startup and the way we try to grow Teamness as a product. We often find blogs on the web for various products which write about their development process and it's an interesting and useful resource.

Writing about product collaboration and management methodologies and how can these be applied to small businesses. Teamness users are people working and collaborating on various projects. Having this topic on the blog could bring new insights for some and could introduce Teamness to them.

What's your opinion about blogs for businesses? Also, what subjects would be of interest to you on this blog?

Friday, October 31, 2008

Feedback for a startup

Every web service needs some kind of feedback mechanism. When working on a startup, feedback is probably even more valuable than when the product is mature. Here are some thoughts regarding the feedback for Teamness and how we're trying to make it easy for our users to make themselves heard.


Image by Orange_Beard

Why is feedback important for a startup?

It keeps you on the right track. You'll focus on the things that users actually demand, beside the ones that you think are desired. This doesn't mean that the features you're thinking about are useless, but it may imply they're less important than you think. Then it comes to prioritizing in an efficient way.

It increases the motivation. When people start using your application, this will constitute a good incentive for you to keep up the work. Getting feedback from them is a way of knowing that they're actually using it.

Situations you didn't consider show up. The diversity of the users generates context you probably didn't think about before.

How do we get feedback for Teamness?

Right from the beginning, we asked ourselves how we can make it easy for the users to send us feedback. As I pointed out in a previous post about support, it's hard to obtain feedback in the beginning stage of a product, because most users just walk away if something doesn't work.

We cannot change this behavior. After all we are all users and act in the same way, but we can make sure there are a lot of options for people to contact us. Here is a list of current choices Teamness users have for that:

1. Direct feedback from any page in Teamness
The user must get in the situation of searching for how to contact us. The method to do it should be right there and this is why we added a link called "Send feedback" in the header of every page. The link sends the user to a page with a simple contact form. Since we added this feature, we received more messages this way than through email.

2. Email
This is how we used to get most of the feedback, before implementing the option above. The emails usually consist in bug reports or feature requests, but we also receive business proposals.

3. Blog
A blog is a good place to improvise in all directions regarding the project. Using a blog you may conduct polls, invite users to participate in discussions and so on. We started blogging here after we launched, but I think that if we would've started before, like these guys did, it would've helped collecting more feedback and in an earlier stage of the product.

4. Forum
We have set up a message forum as an environment for users to provide feedback. However, we observed that most of them prefer the private way of a direct message, like email or the contact form. In any case, a forum is good in the long run, because it's a way of allowing users to engage in conversations about your product amongst themselves.

Don't get carried away

Users want the products they’re using to fit their needs as a glove. However, this is very difficult to achieve, due to the diversity of the necessities out there. We're trying to balance the options we have and to refrain from plunging into implementing a feature that will make life easier for a user, unless it's obvious it will make life easier for many users.

One of the most common advices for small web startups from experienced entrepreneurs is to launch early. A strong reason for that is feedback accumulation for the reasons described in the beginning of this post. Of course, you cannot launch a product that does pretty much nothing and expect users to come and tell you what to do, but providing a single solution for a single problem may be a good start.

Saturday, October 25, 2008

Monitor your web presence

Image by fazen

A celebrity is used to being talked about. A known business is mentioned in too many places to bother keeping track of them. But with a small startup like Teamness we cannot afford not being aware of the places on the web where we’re mentioned.


Why is it important to know where you're mentioned?

We want to know what's being said about Teamness for the following reasons:
  • Start new relationships. Relationships, even web ones, are good for the business. People are more likely to use your product if they know you. And they’re more likely to recommend your product.
  • Participate in conversations about your product. People comment on reviews of your product and sometimes they ask questions about it. Other people make various assumptions, which may be wrong and if left unclear or unanswered, they might create a false perspective over the product. It's a good thing if conversations about your product on other websites are not left undone.
  • Get notice about critical opinions. Some critiques may be wrong and it could be good to correct the perception. You may also come upon nasty comments about your product, perhaps in the forums of the competitors. This is unpleasant, but it's something we don't want to ignore.
  • Find out mentions of your blog posts. If you have a blog in which you promote the product, it's good to know if some of the posts are mentioned. This way you may also track successful posts of your own.

How do we know where Teamness is mentioned?

My favorite method to watch for Teamness on the web is by using RSS feeds. I created a folder called "About Teamness" in Google Reader, which is the RSS aggregator I'm using. Here I added a couple of feeds to let me know where Teamness pops up, by using various features from a few web services, as following:

Technorati watchlist
Technorati allows you to watch various items by using keywords or URLs. In the watchlist page I inserted the “Teamness” keyword and I obtained a RSS feed which I then added in the “About Teamness” in Google Reader. If you don't like RSS (and I noticed there are still a lot of people who don't), you have the possibility to access your Technorati watching list in the page itself, without using the RSS feed.

Google
Type the search term in either Google News or Google Blog Search and along with the search results, you'll get a RSS or Atom feed. I typed “Teamness”, of course, and I then used the two RSS feeds offered by Google.

Twitter
Using search.twitter.com you may input search terms for tweets and you can get a RSS feed. They even offer advanced search capabilities, so you may get only tweets with "positive attitude :)", for instance.

Delicious
Delicious offers a feature called Subscriptions, through which you may subscribe to certain tags used by all the users. I created a subscription for the tag "Teamness" and I also got a RSS feed for it, which went into the "About Teamness" folder. Here is a nice post explaining how to use Delicious subscriptions.


Other ways of monitoring your presence

Using Google Alerts is another way of staying up to date with your presence on the web. Google Alerts are "email updates of the latest relevant Google results (web, news, etc.) based on your choice of query or topic". You may track keywords through various media like news, blogs, web, groups and video.

Other services like TechRepublic or Magnolia offer similar capabilities which may be used in the same way to keep track of your startup.