We’ve dropped product Roadmap silently and it was not a good idea. I want to share the reasons behind this decision as well as our plans for the next several months.

Roadmap Problems

Roadmap has been publicly available over the past several years on our web site. We’d change it time and again and we’d promise something based on the roadmap, but then do not keep the promise. Some examples are Wiki integration and Help Desk Portal re-design. Wiki integration has lived in the roadmap from the beginning, but it is still an idea in the backlog. Some activities have been started on Help Desk Portal, but paused this Summer to focus on other things.

In a nutshell, roadmap was harmful to all parties. Customers relied on it and were disappointed if priorities had to be changed. We we were not able to stick to the priorities due to various internal and external reasons.

Now we have a single goal:

Create a life-changing agile project management tool for small to medium businesses

It means we want to create the best APM tool in the world for small to medium businesses. This is a very challenging goal, but we are really passionate about it and we know how to achieve it.

The short term strategy is very fluid though. There are SO many parts in TargetProcess we want to improve and make them simple, emotional, fast and useful. We know how to do that. The only problem is that we can’t focus on all parts at the same time, we have to prioritize carefully and pick 2-3 top things.

Currently, we think that the most important problems to address are:

  1. Performance
  2. Multiple teams support

Performance

Our ultimate goal is a sub-second response time for all pages on any reasonable load. Many areas in TargetProcess should be improved to make it happen. Currently we are focusing on a new plugins architecture that will significantly reduce server load. The other thing we’ve started is the complete redesign of View/Add/Edit pages. These pages are used most and ironically they are the slowest (even lists are faster).

We got rid of half-backed solutions this year and every major improvement is now preceded with the complete UX cycle incl. concepts brainstorming, prototyping, usability testing etc. Definitely, this slows us down at the start, but the final solutions will be outstanding in our opinion. For example, we are very happy with the navigation improvement this year. It still has some problems, but it was the first attempt to apply UX phase. The next solutions will be even better.

We’ve split into 2 teams that work on solutions almost independently with full focus. New plugins should be released on January and you will enjoy:

  1. Faster (much faster) performance
  2. Nice and easy-to-use API to create new plugins (currently it is quite hard to do)
  3. Mashups. It will be possible to inject UI on TargetProcess pages and create really powerful custom things

View/Add/Edit will be released in small batches and in the end you will have:

  1. Fast and painless navigation to Views everywhere
  2. Full inline edit in Views
  3. Quick Add everywhere

Multiple teams

Multiple teams support is very important for about ~50% of our customers. If you have several teams working on dependent projects, you will enjoy it as well. We believe no tools on the market support multiple teams planning and tracking nicely and expect to really simplify life of many people in agile software development soon.

The first part of the solution is UI to manage and track multiple teams. It is already defined and we are running usability tests to improve it. This UI (we call it ZoomBoard so far) will be included into TargetProcess as a beta this month (November) and you will be able to use it to plan and track several projects.

Then we are going to change business layer to support multiple teams. There is no clear estimate for that so far, but we expect to release it in 6 months. Multiple teams support will allow you to:

  1. Plan and track work on a team(s) level for several projects on one screen
  2. Plan and track releases and iterations on a team level, no matter how many projects the team works on
  3. Have complete visibility on an individual/person level

We know that there were just 2 major releases this year, but upcoming improvements will be outstanding in my personal and highly biased opinion. Only 2 customers participated in ZoomBoard usability tests so far, and here’s their feedback:

The new task board is a hammer! Definitely the best PM tool on the market

It will be a life-changing tool for agile project manager

I am sure you will like upcoming releases. These are significant steps toward our ultimate goal.

Best,
Michael Dubakov
TargetProcess founder and CEO

We’ve got an interesting new tool in TargetProcess 2.18.1 — Bug Pain plugin. It emerged from our own “bug pains”  to empower decision making for QA team as they pull some bug to fix, with no Product Owner involved.

Disclaimer: QA Team are aware of product development strategy, they just needed some help with bugs prioritization when Product Owner is not available to talk.

Bug Pain value in TargetProcess depends on “Severity, “Visibility” and “Class” values as below:

bug-pain-severity-visibility

“Severity” indicates bug severity per se. This could be some grave error that ruins the whole release or a small UX flaw. We’ve got the following “Severity” values:

5 – Much anger & crying – No workaround
4 – Anger & swearing – Difficult workaround
3 – Annoyance & frustration – Easy workaround
2 – Confused
1 – Laugh if notice

“Visibility” indicates how many users are likely to spot bug and how soon. E.g. it takes 10 steps to reproduce bug (random not straightforward steps), in a browser used by 1% of people –  or this is an error on Login Page for 100% users as they attempt to login.  Our Visibility values are:

1 – ~5%
2 – <50%
3 – >50%
4 – ~100%

“Class” shows relevance of bug in the context of product development strategy.  This value can differ for each particular company/project/product.  Speaking of TargetProcess, improving usability is paramount for us at the moment.  So, a bug with usability related Class will be more important than a bug found by Trial User.  Here’re the Classes we’ve got:

1 – No customer, Security
2 – Free/Trial user, Cosmetic
3 – Paid Customer, Usability, Whoops

Bug Pain is calculated based on this formula:

[Bug Pain] = X * [Severity] + Y * [Visibility] + Z * [Class],

where X, Y, Z are specified in the plugin setup (8, 5 and 4 respectively).  These values have been identified experimentally based on common sense for a cloud of bugs and may vary for each particular company/project/product:

bug-pain-calculated-automatically

Next, bugs can be filtered by Bug Pain value.  The most important and urgent bugs will be on top of the list and should be fixed first:

pain

This plug-in is a helpful tool for Product Owners and QA Teams as they prioritize bug fixes.

Bug Pain plug-in comes out-of-the box with TargetProcess now.

Soon (in February) we will release a completely new Tp.Tray. It is a small windows-based application that helps you to capture screenshots and post bugs into TargetProcess really fast. In fact it will be a free screen capture utility with a nice interface and basic functionality.

tp_tray_1

There are many new features and improvements in Tp.Tray. It will be possible to capture several screenshots and store them in a library for future use.

tp_tray_2

Next, you’ll be able to merge several screenshots into one image and edit it as required. Editing is much more powerful and optimized for screenshots with annotations.

tp_tray_3

In the next releases we will extend Tp.Tray with some nice capabilities like:

  • Instant notifications about events in TargetProcess
  • Ability to add Features, Stories and Requests quickly
  • My ToDo list
  • Automatic time tracking

Stay tuned!

Check the new TestTrackPro and Perforce integration videos:

http://targetprocess.com/video/testtrackpro/testtrackpro.html

http://targetprocess.com/video/perforce/perforce.html

After personas creation and scenarios writing, we’ve started UI and flows development.

Here are the screens that allow developers to connect to TargetProcess and query ToDo lists:

Query Selection

And this is a Bug View screen

View Bug

Integration team at TargetProcess is starting Eclipse/MyLyn plugin development. Today we  had the first creative meeting. We created personas, defined their goals and also wrote several scenarios. Here are some photos of the personas:

All personas

We defined four main personas: Developer, Senior Developer, Team Lead, Automated QA. Each persona has behavioral patterns, motivation, etc. Green percentage is  population. For example, we think that about 45% of Eclipse plugin users will be Developers.

developer

Senior developer is mature and experienced. He follows best agile development patterns :)

Senior Java Developer

Team Lead has many interruptions (helping people around).

Team Lead

Automated QA is not very experienced in Java.

QA

We’ve opened Plugins Source Code under BSD license. You may download plugins source code and use them for any purpose. Available plugins are:

  • Tp.HelpDesk.AutoReplyToRequester
  • Tp.HelpDesk.BindEmailRequestToProject
  • Tp.Integration.External.Bugzilla
  • Tp.Integration.External.Jira
  • Tp.Integration.External.TestTrackPro
  • Tp.Integration.SourceControl.Perforce
  • Tp.Integration.SourceControl.SourceSafe
  • Tp.Integration.SourceControl.Subversion
  • Tp.Integration.Testing.TestRunImport
  • Tp.Integration.Testing.TestRunImport.NUnit
  • Tp.Integration.Testing.TestRunImport.Selenium

The goals of plugins source code sharing are:

  • You may modify plugins to fit your needs.
  • You may create new plugins based on existing plugin. For example, you may want to import test run results from Fitnesse or another system.
  • You may fix bugs in existing plugins and submit us patches :)

Feel free to ask any questions about plugins development.

You may download Bugzilla Integration and Subversion Integration plugins source code and improve them as required for your own needs. These source code released under BSD license.

We are starting development of TargeProcess Add-In for Visual Studio 2008. It will be released in v.2.9 (in April). The functionality is quite simple. There will be a ToDo list with integrated Time Tracking abilities. Not a rocket science, but really helpful thing for .NET developers who don’t like anything unless it has VS add-in ;) .

TargetProcess v.2.8 release took longer than expected. The reason as always is changing requirements :) When we planned release roadmap we thought Bugzilla integration going to be easy and release will be quick. But when development started, we decided to add Plugins Framework into TargetProcess.

Why? We have many requests about different features. If we will implement them all, it will kill the product. Moreover, it will take YEARS to implement at least half of them. Plugins give us flexibility. In many cases we will not say “No, we think this feature is not required to other customers and will not implement it“. Instead we may say “Ok, if you need it you have two options: implement it as a plugin or request customization service and we will create the plugin for you“. Sounds better, isn’t it? And it do resolve the unique problem that company has.

So far plugins allows you to operate with business logic only. There are no API for UI widgets you can create, but we will add them in future. Still plugins framework provides a real customization power:

  • You may influence entities workflow and do literally any action you want.
  • You may integrate with almost any external system (for example, now integration with another bug tracking tool will take about a week!).
  • You may create specific reports and gather required data.

There are many possible applications, creativity is enormous thing when it is supported by flexibility.

That was a big addition and it took time to implement and polish. Still we don’t even expect it is complete neither “perfect”. We pretty sure that first real usages will show us the best road for improvements.

Bugzilla integration was implemented as the first real plugin. It synchronizes bugs in Bugzilla and TargetProcess, thus separating bug tracking and planning concerns (use right tool for right job). The plugin provided with full source code, so you may customize it as required.

Other significant improvement is better custom fields support (look, almost all new features are about flexibility!) Now custom fields may be defined for each process. One team may define Risk for user story, while another doesn’t. Now TargetProcess supports that. Custom fields were added into Custom Reports (they have similar names, it would be the crime to not integrate them). Also custom fields now visible in ToDo list and in Iteration plan (with filters).

As a final note, we fixed more than 50 issues in v.2.8. Most of them are small, but annoying (for example, semicolon separator in CSV export or filters remembering in Iteration Plan).

BTW, we have nice plans for v.2.8 like Visual Studio plugin and Test Track Pro integration. Enjoy the trip!

© 2012 TargetProcess Product Blog Suffusion theme by Sayontan Sinha