We're excited to add a new entry to the 3rd party tools directory: Aragorn, the first Pivotal Tracker client for the iPad.
The first version of Aragorn supports read only views of your projects and stories within them. Thanks to @elight for writing the app!
Our managed hosting provider experienced an extended network outage today, which affected a number of applications including Pivotal Tracker.
The outage was caused by a failure of a primary network load balancer. Network engineers have replaced the load balancer, and are in the process of investigating why traffic did not fail over to a secondary load balancer as expected. They will be performing a fail over test early this morning, from 1am PDT to 3am PDT, during which time some Tracker users may experience increased latency.
We appreciate everyone who notified us about this outage, and apologize for the inconvenience of not being able to access your projects this morning.
Three interesting new user-contributed Pivotal Tracker tools have been added to the growing 3rd party tools list this week:
Pivotal Tracker Story Board
From vizio360, this is a Google Chrome extension that allows you to visualize your current iteration as a card wall, with columns for each story state.
whereuat
Adds a slide out panel to your rails app that directs clients to test stories that have been marked as 'delivered' in Pivotal Tracker. Thanks to PLUS2 for this one.
Pivotal Attribution
Text-based tool for tracking story completion per-user on Pivotal Tracker, from Joshua Szmajda.
We're looking forward to trying these on some of our own projects at Pivotal. Thanks to everyone who's shared their work with the Tracker user community so far, and let us know if you've written something new that you'd like to share.
We received notification from our hosting service provider Engine Yard, about scheduled data center maintenance tonight (Tuesday Aug 3) starting at 11pm PDT, lasting approximately one hour.
During this maintenance, Engine Yard's infrastructure partner Terremark will be updating the configuration of spanning tree on network switches, to be able to hot-add resources in the future. A direct outcome of the maintenance will be increased network stability.
During this maintenance window, Tracker may experience high latency or downtime for 5-10 minutes at a time. There may be a number of short latency/downtime periods during the window.
There appears to have been a data center outage early morning, affecting a number of applications including Pivotal Tracker. This has caused connectivity problems for users in some locations, and it appears to still be persisting for some.
We're working with our hosting provider to get this resolved as soon as possible, this is our top priority.
This is the second data center outage this week. At the moment, we do not have enough information to know whether the outages are related.
Also, we have received reports that Tracker has been unreachable from certain parts of the world (including China) since the migration to a new data center last week. We've filed a request with Engine Yard to investigate, and hope to have this resolved soon.
Our apologies for the inconvenience these outages have caused. We'll post more information here as we receive it. You can also follow @pivotaltracker on Twitter for updates.
I often hear questions from Pivotal Tracker users about how to organize teams and projects. We also see many requests for features that would make it easier to see stories from across multiple projects.
Tracker is designed for full immersion in one project at a given time. This stems from how we work at Pivotal Labs.
We organize teams such that a single team (and the people on that team) have a single backlog (and Tracker project). This means that within a team, there are no conflicts in terms of priorities, there is less context switching, and the team is completely focused. It leads to more consistency from iteration to iteration and therefore a steadier velocity, which allows you to have a more accurate insight into how long the rest of the backlog (or a release) might take to complete.
We also make it so that anyone on a given team can grab the next available story from the top of the backlog (or the current iteration). This implies few or no specialists (there is no back-end guy), and is generally referred to as collective ownership. It increases overall efficiency by allowing the team to dynamically re-balance, and minimizes reliance on any individual person (which among other things, leads to more relaxing vacations for developers).
The project's customer (or product manager) focuses on prioritizing stories in the backlog, and the development team is collectively responsible for delivering software based on the backlog.
We use labels to tie related stories together within a project. These can represent a major feature, specific end customer, etc. Labels can help answer questions like, how much work is left in this large feature?
A single backlog for the entire team does put more work on the plate of the owner of the backlog (customer / product manager), as he or she has to constantly make potentially difficult prioritization decisions, but, thinking hard about priorities is a good thing, and it allows the development team to focus on getting more work done. That ultimately makes everyone happier.
Also, there are people in certain roles (for example executives and designers), that given their nature, tend to be involved with multiple projects at once. Tracker could certainly use some features to help these roles, and we're thinking about these, but overall, it's more oriented towards enabling the immersed team.
A single team/project can get large enough to the point where it becomes challenging to manage a single backlog. For us, this point is generally reached with 5 to 6 pairs of developers (or 10 - 12 people). Assuming that more developers can actually add value to the overall project (this is not always the case), it's probably worth considering splitting the team into multiple smaller teams, each with their own single backlog.
To avoid knowledge and cultural silos with multiple teams, we find it helpful to rotate a few people around teams every iteration. It's important to maintain consistency (and therefore a steady velocity), so you don't want to shift too many people around too often - usually rotating just 1 person (on each team) each iteration is enough, assuming you're pairing and switching pairs within each team often.
In a multi-team (and Tracker project) environment, the product/project manager acts as a load balancer, and allocates work across the multiple teams/backlogs by considering velocity, dependencies, etc. This is typically a full time job. Tracker doesn't have much out of the box to help with this, but we're thinking about this as well, although it may be that some of this kind of work is better done in a spreadsheet, or other, more traditional project management tools. (As a side note, we did recently add the ability to move stories between Tracker projects, making things a tiny bit easier for people who manage multiple teams/projects).
I'd love to hear your thoughts on any of this, including suggestions for how to organize large projects and multiple teams (and how Tracker can help with that).
Pivotal Tracker is moving to a new private cloud hosting environment at Engine Yard this Thursday, July 22, starting at 8pm PDT.
Planned downtime is approximately one hour, but because we're changing IP addresses of the Tracker servers, it may take longer for DNS changes to full propagate.
If you've opened your firewall to a specific IP address for Tracker integrations, you'll need to make changes. We'll post the new address of the integrations server after the move, you can also 'ping api.pivotaltracker.com' to resolve it.
Apologies for the inconvenience, we're hoping for noticeable performance improvements in the new environment.
With Github's help, we've added Pivotal Tracker to the list of Github's built in service hooks, making it easier to tie commits to Tracker stories.
To set it up, go to the Repository Administration section of your Githup repo, click on Service Hooks on the left, and choose PivotalTracker from the list. Enter your API token, and you should be good to go.
More on Tracker commit hooks on the API help page.
We're forming a Tracker User Group in the windy city, and the first meetup is scheduled for Jul 22, at the Hashrocket Chicago office.
I'll be there to talk about the concepts and history behind Tracker, our experience with it, and will give a demo to those that are interested. It's a great place to give feedback and ask lots of questions.
Space is limited, so RSVP soon.
For the next month or so, we will be rolling out a series of changes to various parts of the Tracker server architecture, including moving to a Memcached distributed cache for certain requests, cookie based sessions, switching from Mongrel to Passenger, splitting the very large history table, etc.
We're doing this to improve performance, and eliminate potential scaling issues as our traffic grows. To reduce risk, we'll introduce these changes in separate updates, once a week.
These updates will occur on Wednesdays at 7:30pm PDT (including tonight), and last under an hour each. If there are any long running migrations needed, we'll plan them for weekends, or handle them incrementally, to avoid any extended down times.
We understand that these week night outages are inconvenient to many of you, especially in Asia. We apologize in advance, and will try and keep the updates as brief as possible.