Pivotal Labs

Main menu

Skip to primary content
Skip to secondary content
  • About
  • Case Studies
  • Team
    • Executives
    • Locations
      • San Francisco (HQ)
      • Boston
      • Boulder
      • Denver
      • London
      • Los Angeles
      • New York
  • Community
    • Blogs
    • Tech Talks
    • Events
  • Careers
    • Lifestyle
    • Principles & Practices
    • Benefits
    • FAQ
    • Apply
  • Contact
    • Press Room
    • Press Releases
    • In The News
    • Press Kit
  • All
  • Labs
  • Standup
  • Tracker
Pivotal Labs

Jeff Sutherland on using Pivotal Tracker for Scrum Projects

Pivotal Labs
Tuesday, September 1, 2009

Jeff Sutherland, one of the creators of Scrum, has just posted a new blog entry in his Scrum Log: Pivotal Tracker: Now with a Burndown Chart!

I first met Jeff when we were both presenting on Agile process to a forum of OpenView Venture Partners portfolio companies, and have been a big fan of all he has to say about the adoption and effectiveness of agile practices in the wild.

Many thanks to Jeff for his help to make Tracker a better tool for scrum. We’ll keep working with him to make sure Tracker is the best scrum tool it can be.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

BizConf

Pivotal Labs
Monday, August 24, 2009

I just spent a wonderful weekend with 75 of the brightest folks I know in the Ruby community. My hat’s off to Obie and the Hashrocket crew for putting together a really great, intimate conference in a beautiful location. It’s refreshing to really have to struggle to choose which talk to attend from so many choices at each session. I know too many choices are a Bad Thing™, but the format made for great small sessions, and a wonderful thing happened: Everyone got to really meet and get to know everyone.

Among many others, I had the pleasure of meeting CJ Kihlbom, who nails a lot of why these conferences are so important in his post, The Business Value of Conferences.

It was really pleasant to present to a community of business leaders who understand the value of agile, and who are serious practitioners in their own practices.

A lot of you have asked for the slides from my talk, Agile, Rails and the Cloud, so I’ve posted them here.

Those of you who thought about coming but didn’t really missed out. Come next year. You’ll be glad you did.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

First Tracker Users Group meeting a success

Pivotal Labs
Friday, May 1, 2009

On Wednesday night we hosted our first San Francisco Tracker Users Group (SF.TUG)

It was a great opportunity to meet more of our users, and hear directly from them about how they’re using the product, and share with them some of the philosophy behind it.

We’re excited by your enthusiasm and we will definitely make the TUG a regular event here in San Francisco, and we are planning to start one in our New York City offices soon. Please visit the Meetup group to join the discussion, and for more information and the schedule for future meetups.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

Pivots Speak on Scalable Teams

Pivotal Labs
Friday, March 20, 2009

Last week, Wolfram Arnold of RubyFocus interviewed Edward Hieatt, our VP of Engineering, and Davis Frank, one of our engineers, to try to get at the heart of how you build a scalable software development team.

The interview is posted on RailsLab, at
http://railslab.newrelic.com/2009/03/18/scalable-teams-part-1-communication

It’s a nice piece. We look forward to the second installment.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

Pivotal Tracker wins the Jolt Award

Pivotal Labs
Thursday, March 12, 2009

I’m very pleased to announce that Pivotal Tracker has won the coveted Jolt Award, in the Project Management category.

I want to thank the judges for selecting Pivotal Tracker above a category dominated by Agile project management tools, and for rewarding Tracker for innovation.

I want to thank the community who have used, evangelized, and supported Tracker, and in particular Obie Fernandez, Ward Cunningham, and Nivi; plus everyone over at Engine Yard for hosting the app.

And of course I want to thank and congratulate the development team and visionaries, particularly Dan Podsedly, Alex Chaffee, Rob Mee, Mark Michael, and Edward Hieatt for envisioning and then building the tool that we’ve come to depend on.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

Pivotal Tracker a Finalist for the Jolt Awards

Pivotal Labs
Thursday, December 18, 2008

I’m pleased to announce that Pivotal Tracker has been selected as a finalist for the 2008 Jolt Awards. Thanks to everyone on the team for putting so much care into Tracker, and making it what it is today. Winners will be announced March 11, 2009 at SD West in Santa Clara.

Wish us luck!

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

Pivotal Tech Talks now available on iTunes

Pivotal Labs
Tuesday, December 16, 2008

For the last year or so, we’ve been inviting speakers to come visit us and talk about interesting things in the Ruby/Rails space, the agile space, and on topics related to software development in general. We see it as a great way to keep our developers on the cutting edge, and a number of speakers have used it as an opportunity to gather early feedback from our team. We’ve found the talks we’ve had to be very valuable to us, and are pleased to share them with the larger community.

To that end, we’ve posted a selection of our talks to our talks page, and also made them available via the Podcast section of the iTunes Store in both audio and video format.

We’ve also had a number of panel discussions in our Project Startup and are posting those talks as well.

We’ll keep posting talks as we have them. If there are topics you’d like to see, or topics you’d like to present, please email us!

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Christian Sepulveda

Innovative Software vs. Commoditized Software

Christian Sepulveda
Monday, April 2, 2007

Most of software development can be considered from one of two perspectives:
Is it innovative or can it be considered a commodity?

Starting with the latter case, these software projects are a re-implementation
of software that has already been written numerous times. It is even possible
to buy existing applications and integrate with other components or implement
minor customizations. An example of commoditized software are shopping carts.
Years ago, in the early Internet, merchant websites and shopping cart
integration was expensive and required significant development; today I can
pay an extra $20 a month in web hosting for the same functionality.

For a commoditized software project, it makes sense to look at low cost
development options. These frequently employ overseas developers, thousands of
miles away in other time zones. With commodity software, the requirements are
well understood and many exemplary models exist. Communicating project
requirements and expectations is easier, so the risks are far lower.

Innovators don’t have such ease; requirements change often and are foggy at
best. Building from existing components is either unfeasible or requires too
much customization (the dreaded “integration tax”). This poses a great
challenge for an entrepreneur, as being first mover may be more of a risk than
an advantage. Large amounts of time and money can be expended while the
entrepreneur searches for her actual market opportunity or the proper way to seize it.

Incremental and iterative development can help mitigate these risks for the
innovator. With each iteration, the innovator has feedback that allows her to
tune and adapt requirements, converging on essential functionality and
de-emphasizing tangential functionality. For an entrepreneur with a limited
budget, efficient use of development resources is critical.

While iterative development can keep you focused, it is not enough. Close collaboration and
interaction with developers is also key. Building a rapport between product
visionaries and those executing this vision not only creates a common sense of
ownership, which leverages “collective brain power”, but it forces the
entrepreneur to clearly communicate her vision. Too often innovators have a
muddy understanding of their own ideas. (A technique called “high concept” is
another good tool for entrepreneurs and will be the subject of a future post.)

Unfortunately, many entrepreneurs treat their venture as commodity software,
as they attempt to outsource development to low cost programming body shops.
While I have a particular bias in this case, the real question for an
entrepreneur is: If it is so easy to outsource your innovation, is your idea
actually novel? Are there any barriers to market entry for a competitor? These
questions are important to address before any development investment is made,
regardless if the software is being treated like a commodity or an innovation.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter
Pivotal Labs

A Different Take on Startup Incubation

Pivotal Labs
Saturday, March 31, 2007

About a year and a half ago, Pivotal Labs started a new practice, focused on product-led startups. It’s not the traditional VC/EIR model though. With Pivotal, our clients are the ones with the product vision. They’re the entrepreneurs. We focus on bootstrapping development, and getting the engineering effort going. We’re just here to make sure the technology works, and that engineering execution doesn’t get in the way.

When we take on a project, we like to hit the ground running. We seed the project with an experienced team, ready to begin executing immediately on the client’s product vision. As the vision grows and changes, our team adapts. Usually the client will start hiring their development team as development continues. Often, we’ll help them recruit and interview. Then we’ll weave their new folks into the team, teaching them the code base, and all our techniques as well. We want to make sure that when we’re done with the project, their team can move into the next phase of development with confidence, and keep things running smoothly.

When our clients already have an established development team, we weave our developers in with theirs, and co-develop with them. If they’re new to agile, we teach them agile practices by doing, as we write code with them. Rather than dropping in with a day-long lecture based on toy problems, and then vanishing into the sunset, we show them how agile works, in their own development environment. We fill in any gaps in their design, modeling and testing skills, and generally improve development practices as we go. Once they’re self-sufficient, we weave our developers back out, and move on to the next engagement.

Build-Operate-Transfer

Rob Mee, our founder and CEO, likes to borrow a phrase from the civil engineering world to describe how we engage with start-ups: Build-Operate-Transfer. When an enterprise is first getting started, they typically don’t have the engineering resources to get going quickly, and can lose months of lead-time trying to build a team. That’s where we come in: Our job is to take our clients from a standing start to a fully functional product, something we can typically do in a few months. Once things are up and running, we’re ready to turn over the reins, and let their team run things for themselves.

Flexibility

One thing that’s special about us is that we can vary the team size on demand. During the early stages of development, start-ups will often have big fluctuations in workload. We can ramp the team size up or down, depending on development objectives and financing constraints. We can develop at full speed for a week, a month, or a year, then stop on a dime—and stop burning capital—and stop for as long as it takes for the client to close a funding round, or get some traction in the marketplace, or decide on the next round of features. Our clients are done with us when they decide they’re done. Their business goals and product needs are always in the driver’s seat.

We strive to be a strategic partner for our clients. We are not an outsourcing firm but instead work to get our clients self-sufficient. We believe our approach offers a unique balance between the short term need for execution and the long term need of sustainability.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter

Topics

  • agile (778)
  • rails (113)
  • testing (87)
  • ruby (83)
  • ruby on rails (70)
  • jobs (62)
  • javascript (54)
  • techtalk (44)
  • rspec (38)
  • activerecord (29)
  • productivity (29)
  • gogaruco (29)
  • ironblogger (29)
  • git (28)
  • nyc (27)
  • rubymine (25)
  • bloggerdome (22)
  • mobile (22)
  • cucumber (20)
  • process (19)
  • pivotal tracker (19)
  • jasmine (19)
  • design (18)
  • ios (18)
  • webos (17)
  • objective-c (17)
  • android (16)
  • palm (16)
  • "soft" ware (16)
  • fun (15)
  • tracker ecosystem (15)
  • ci (15)
  • cedar (15)
  • rails3 (14)
  • performance (14)
  • bdd (14)
  • gem (13)
  • tdd (13)
  • selenium (12)
  • css (12)
  • goruco (12)
  • bundler (12)
  • meetup (11)
  • railsconf (11)
  • nyc-standup (11)
  • capybara (10)
  • mac (10)
  • mojo (10)
  • chef (10)
  • api (10)
Subscribe to process Feed
  1. ←
  2. 1
  3. 2
  • About
  • Case Studies
  • Team
  • Community
  • Careers
  • Contact
  • Labs
  • Events

Contact Us

contact@pivotallabs.com
+1 415-77-PIVOT
TwitterLinkedInFacebook

Pivotal Tracker

Tracker is the award-winning agile project management tool that enables real-time collaboration around a shared, prioritized backlog.
Visit pivotaltracker.com >