Posts Tagged ‘agile’

From Agile Software Development to Agile Management [INFOGRAPHIC]

Ten years after the Agile Manifesto was signed by an impassioned group of software developers in Utah, the processes and principles outlined in the document have begun to infiltrate areas of business outside software development.

For the newbies, Agile is a software development methodology which promotes adaptive planning, a time-boxed iterative approach, evolutionary development and delivery, and a rapid, flexible response to change. Guided by 12 principles, Agile development puts an emphasis on results, productivity, fact-to-face communication, collaboration over negotiation and most importantly, satisfying the customer through the quick delivery of software.

After a decade of helping small to medium firms execute more efficiently, development and corporate IT managers have gotten the word about Agile and we’re now starting to see its methodologies put to use across the enterprise.

At Gist, we’ve deployed Agile practices throughout marketing, product development and even to our funding rounds and high-level corporate goals. A closer look at our New Workstyle philosophy reveals the strong influence of Agile methods on our individual workstyles too. We just think it’s the right way to get stuff done. As shown in the infographic below, Gist’s Agile method comprised an 18 month ‘horizon’ focus on big corporate goals; six month ‘directional’ focus on product-centric goals; three month product roadmap; one month long marketing themes; two week long dev sprints; and one sprint in preview (less than 100-200 limited release for tricky new features and rollouts).

In researching exactly how Agile processes are spreading across businesses in new industries, we found some very cool stats:
1. 66% of Agile firms say they complete projects faster (tweet that stat)
2. 78% of Agile firms say accelerating time-to-market was the biggest reason for adoption (tweet that stat)
3. Bigger companies are turning to Agile: 32% of firms have 250+ employees (tweet that stat)

Enjoy and share this visual representation of Agile’s core tenets and trends and leave a comment if you’ve experienced an increase in productivity using the Agile method in your business.

Scrum Much? Agile Development By the Numbers

2010 was a great year at Gist and we thought it would be cool to take a look back at our performance from a year of Agile Development. It is amazing to see how much a team can accomplish when everyone works together to make it happen. For all you numbers geeks out there, here are some interesting stats and observations from the past year:

1. Shipped 25 releases. (Almost a release every 2 WEEKS!)
2. Ten iPhone releases.
3. Three Android releases.
4. Fourteen Gist for Outlook releases.
5. On top of all that, we also launched new apps for Google AppsLotus NotesFirefox and Chrome.

When Work Gets Done

One really interesting thing we found was our “Work from home” day (Thursday) had more commits than any other day between the hours of 6 p.m. and midnight. I guess it shows that people actually can work from home but they just do it on their own time and make sure it gets done by Friday. Another observation was that the only time throughout the entire year that nothing was committed was Saturday at 6 a.m. (Check out the white space on the chart below)

Also, the most active hour of the day over the entire year was 5 p.m. which proves the “Parkinsons Law Theory.”

Work expands so as to fill the time available for its completion.

Don’t Forget About Coffee

We have a pretty amazing coffee machine in the Gist office and it has made over 7998 cups of coffee since we purchased the new machine. (Totally makes our pricey “Jura Impressa F7 Automatic Coffee Center” worth it!)

Thank You and Here’s to 2011

We don’t plan on slowing down and will keep the pace moving even faster in 2011 (Scrum of Scrum anyone?) Thanks to all of you who have been with us along the way and if you are a developer who likes coffee and want to be a part of this post next year, check out our job openings here.

How does your team do development? We’d love to talk more in the comments!

Building a company is about the journey

Gist Team and Mount Si

The Gist team works together

Team Effort Makes the Plan a Reality

The Gist team recently took a day off from coding, talking to customers, and doing the business of a company to do something physical and tangible: climb a mountain.  Fueled by donuts, energy bars, and sandwiches, we made it to the top of Mt. Si in North Bend, WA, a 2700′ rise and 8 mile round-trip hike, and completed the task as a team. We started our task at 10am, made the top of the mountain around 2pm, and returned triumphant to the bottom of the mountain at 4:30pm.  Our journey embodies the process of building a company, one step at a time.

Not all of the paths are charted.

When you build a company, you don’t know all of the paths that you might take.  On our mountain climb, we didn’t know exactly how long it would take, didn’t know initially where we might stop along the way to rest, and didn’t know where our pace might not match with our ability.  But we knew our goal: to get to the top of the mountain with the whole team.   We were able to mesh our styles — some of us are world-class climbers, while others are merely world-class coders and testers — and work together as a team to reach the top.  We all felt a little bit uncomfortable: fast people had to go slower than they wanted, and the slow people had to go faster than they wanted (and Ally the Black Lab probably covered more ground than anyone.)

All the decisions won’t be perfect.

We didn’t know exactly how we would feel getting from the bottom of the mountain, reaching the top, and coming back down again.  But we knew the path — at least some of the trail was well-worn — and other aspects needed continuous improvement.  Did we have enough water and supplies?  Did we need to stop at some points where others wanted to go on?  We made the best decisions we were capable of at the time, and then corrected when we hit a wrong path.  When we made a decision, we sometimes relied upon the actions of a few leaders, and made other decisions as a group.

The important thing is to get back on the right path quickly.

At Gist, we go through this task every two weeks.  Using an Agile development process, we plan our next set of work, agree on how much work it will be, work together to produce a new feature or version of the product, and release it.  It’s not always a seamless task: sometimes the mountain is more forbidding and treacherous and we have to go back up the mountain when we think we’re done to rescue a member of the team, and other times the sun is shining and we all finish in record time.  We are a team and we climb our mountains together — we hope our product reflects this shared commitment.

It’s hard to keep track of what everyone in your network is doing. That’s why we created Gist. Gist helps you build professional relationships by serving you the right information at the right moment to get a meeting, deliver an amazing pitch, or just find a better way to make a connection. We would love you to try out Gist here.

To view a 90 second video of exactly what Gist does, click here.

You can follow Gist on twitter here or join us on our facebook fan page here.

You can subscribe to the RSS feed here or have the latest post delivered to your email inbox here.

This post was written by Greg Meyer, Customer Experience Manager at Gist. Feel free to contact me with questions, feedback, or if you just want to say hello at greg@gist.com.

Tools We Love: Sharing to Evernote from Gist

Share to Evernote Directly from Gist

At Gist, we believe that part of the business of being an agile startup is to make use of other great tools out there that help us to be more productive from anywhere.

One of these tools is Evernote — a service that helps you to save ideas, things you see, and things you like — which we use at Gist on our mobile devices and to save notes on “the next big thing” or just “the next big thing today.”

If you’d like to use Evernote to save things you read in Gist, it’s easy!

How to Get Started

  1. Open an Evernote account — you can do this at the Evernote web site.
  2. If you have an existing Evernote account, find the “Emailing to Evernote” information at the Evernote Account Page; this will be an email address that looks like “[username].7c349 @ m.evernote.com.”
  3. Add a contact to Gist for this account — you could name it “Send to Evernote” or just “Evernote” — or send a message to Evernote from a Gist-connected email account or contact source (such as Gmail, Google Contacts, Outlook, or an IMAP-enabled email)
  4. Now, you can share content from your Gist network with Evernote — simply pick the email sharing option, and type in “Send To Evernote” or “Evernote”
  5. Your shared content will show up in your Evernote notebook.

If you’d like to tell us about your favorite tool or service that saves you time and improves productivity, let us know at feedback@gist.com.

It’s hard to keep track of what everyone in your network is doing. That’s why we created Gist. Gist helps you build professional relationships by serving you the right information at the right moment to get a meeting, deliver an amazing pitch, or just find a better way to make a connection. We would love you to try out Gist here.

To view a 90 second video of exactly what Gist does, click here.

You can follow Gist on twitter here or join us on our facebook fan page here.

You can subscribe to the RSS feed here or have the latest post delivered to your email inbox here.

This post was written by Greg Meyer, Customer Experience Manager at Gist. Feel free to contact me with questions, feedback, or if you just want to say hello at greg@gist.com.

How does an agile software product get built, anyway?

At Gist, we roll out a new release every couple of weeks (and name them after elements on the periodic table) based on all of the great feedback we are getting as well as new features we want to share plus a few bug fixes along the way.  Each release cycle is called a “sprint.” Here’s the story of one recent sprint written by Eric Artzt, one of our outstanding product developers.

We try to release every two weeks, usually on the Tuesday, following one day of sprint planning, six days of development, and three days of testing and stabilization. Sprint planning at Gist is a quasi-democratic process. Work items arise from customer requests, strategic goals, and grass roots initiatives from the team. They are then pitched, fleshed out, reviewed, and approved for development.
Here are some photos taken during Copper sprint planning.
This site is protected by Comment SPAM Wiper.