This is like a hackers guide to levelling up in the software development world. If you don’t know a lot about Agile, software development practices or customer development read through the following books and you’ll be conversational.

Business Model Generation – Alexander Osterwalder

The product management team at Atlassian picked this up back in 2010. It won’t take you long to read through this book – the exercises are the key takeaway and you will need to set aside time for those.

Ash Maurya riffed on this and came up with the Lean Canvas which is aimed at entrepreneurs. You can use Confluence to build lean canvas’ too.

The Lean Startup – Eric Ries

I was fortunate enough to interview Eric at Summit 2012. Fascinating stuff to be found in The Lean Startup.

All of Eric’s writing evolved from Steve Blank’s book The Four Steps to the Epiphany, now superseded by The Startup Owner’s Manual. I am yet to read The Startup Owner’s Manual, but I did catch Steve’s keynote at SF Agile - gold!

The Principles of Product Development Flow – Don Reinersten

Dave Thomas from Bedarra swears by this book, and that is recommendation enough. Get it.

Kanban – David J. Anderson

My introduction to Kanban. Should be yours too.

Honestly, this was behind a lot of the movement that we did in GreenHopper towards Kanban. Lots of folks have taken Kanban beyond software development as well, for example see Chris LePetit’s talk at Summit 2012.

Continuous Delivery – Jez Humble, David Farley

You’re heard of the DevOps movement, right? Take a deep dive into continuous delivery with this book. Jez has been working with ThoughtWorks for a number of years developing their CI/CD offering called Go. In practice you should use Bamboo though - in my biased opinion Bamboo is a better tool!

Scaling Software Agility – Dean Leffingwell

Dean is one of the fellas that has been with Rally since the early days. He spends his time helping Enterprises scale agile. While this isn’t for everyone today, it may be useful as your company grows.

Last Wednesday I had the good fortune to attend Culture Con 2012, and let me tell you, it was brilliant! I wanted to share what I learned at the event as there was some gold! First off, kudos to Dyn for organising and Zendesk for hosting the event.

Culture Con, surprise surprise, was all about the culture of a company. For some people it touched on entitlement, others were interested in hiring for culture fit, some wanted to know how to build a culture and others wanted to know how to keep a culture alive as the company grew. The audience was primarily HR Directors of technology companies. I have a new found appreciation for what these HR Directors do day-to-day, and the challenges they face. Hat tip to Julie Rogers and the Atlassian Talent team for putting up with all of the Atlassians and their needs and wants!

People are Assets, not Expenses

Hal Halladay of Infusionsoft brought something interesting to my attention: business managers should be looking at people today as they looked at factory machinery in the 20th century – as a tangible asset that lives on their Balance Sheet, as opposed to an expense that is only present on the P&L. In the 20th century with the explosion of factories during the industrial revolution labour became part of the production lifecycle. However, labour was seen as an expense as one person could be easily changed for another. Labour was not a fixed asset that lived on the balance sheet like a machine.

Fast forward to the 21st century and we are still treating labour as an expense on the Balance Sheet. As an employee you are an expense, part of the COGS (cost of goods sold) of a product. However, you and your tacit knowledge do not appear on the Balance Sheet. This, despite the fact that you are not easily replaceable, despite the fact that today labour is the largest expense of these technology companies.

So, what do we do? Well, companies have been manufacturing assets in the form of IP that stifles innovation, while at the same time we see AcquiHire become commonplace. These seem at odds. We are acquiring companies for their talent but we can not add that to our balance sheet as anything except goodwill. And we pursue IP that is so broad and vague that any company could be at risk of being sued into oblivion.

Hal argues that we need to start looking at labour in a different manner, that it is time to start treating your employees as an asset on the Balance Sheet. Of course, the GAAP (generally accepted accounting principals) doesn’t support this today, so we can’t just make the change. Something to ponder for your own company.

Building a Culture

There were a number of speakers on this topic throughout the day. A few of the tips from Mikkel Svane of Zendesk were really valuable as he was sharing how Zendesk was scaling quickly while retaining their culture. A few of the suggestions that I picked up on:

Cross-functional Outings

I think the cross-functional outings could be really useful. For example, Support and Engineering, or Talent and Sales. We don’t do anything like this at Atlassian today so it is something I am going to try. Usually we’re doing outings within our team, not more broadly.

Buddy Lunch

Buddy lunches are something we certainly do at Atlassian today – I was Mike Sharp’s buddy back in the day, and Michael Knighten was mine. They are a lot of fun and work well. One interesting twist is that at Zendesk they give a gift card for the lunch to the new employee instead of the buddy. They found that this approach led to the lunches happening sooner, often in the first week as opposed to a few weeks later when the existing employee (the buddy) had time – which is too late to make a first impression.

Company Yearbook

I can’t actually remember if this was from Mikkel or someone on the panel which followed his talk but I thought the idea of a company yearbook was killer. Every December you get a one-pager from each employee and put it into a yearbook like you had at high school. This could be online or printed. Share what you worked on, your great achievements for the year and post a photo. Not too hard. Killer idea. I think I’ll get this one going at Atlassian this December.

Bi-Weekly Onboarding

Evan Wittenberg of Box shared how they were able to scale to 100 new hires a quarter by dropping back to bi-weekly onboarding. They got the same throughput by moving 50% of the hires forward one week and the rest back to the following week – freeing up his teams time and also that of the department heads that would present to the new hires every week. Interesting for me was that a few people mentioned a one week onboarding process while Atlassian has a six week onboarding and all the new hires proceed through it together. It is called Bootcamp and Ted Tencza spoke on this at Summit 2012.

Leadership Lunch

At Atlassian we have Founder lunches for all new hires. The Leadership Lunch takes this one step further by making one member of the leadership team available once a month for lunch. It allows employees to sit with an executive and ask them questions, even if they are not a new hire. I really like this approach for bringing Q&A to a casual setting for all employees on an ongoing basis, especially as a company scales. Great idea.

Value the Culture

Unfortunately VC’s don’t seem to value culture very much today according to one of the panelists, although they should as it is key to getting to product/market fit quickly. If you have a team of awesome people but they can’t work together well and self-organise then you are not going to get anywhere. Great point.

It also seems like some companies don’t value the culture – particularly when they are VC backed or owned by PE. These companies are driven by results, culture be damned. Boy it would be hard to work in a place like that!

Internal NPS

One way to measure the culture of a company was to conduct an internal NPS. Every quarter send an NPS survey out to the employees, asking questions like “How likely are you to refer to us as a great place to work?”. Love this idea. At Atlassian we use the Mood App which is an iPad app that rotates through questions. There are iPads at the doors for every office globally and people press one button (1 – 5 using smily faces) to show how they feel about the statement today. Our Mood App is not as scientific but it is still a great barometer. Either way, there is room for improvement at Atlassian in this regard.

Skip Lunches

An interesting approach to getting a feel for the culture in different departments of a company. In this approach you cut out the manager and a member of the HR team takes a team for lunch. So, you’ve got someone from the HR team taking the three/four/five/whatever number of people from one team out to lunch without their manager. An interesting approach, not sure how I feel about it cause it kind of negates our open company, no bullshit value. Perhaps this would work better somewhere else.

Dream Manager

How about this fella: Donavon Roberson, Dream Manager at Infusionsoft. Infusionsoft value their culture so highly they have recently hired a dream manager whose job it is to help employees acknowledge, articulate and achieve their dreams. What is your dream?

This, to me, seems very freaking progressive. I don’t know what to make of it and want to learn more. Thankfully Infusionsoft have a whole host of resources around their culture. Check it out.

One thing that Donavon mentioned was that they had distilled the five levels as described in Tribal Leadership down to two things – introvert and extrovert. He felt it was possible to use this gauge to identify how to work with different people and move them up to the next stage.

ELF’s

Emerging Leadership Forum was a really novel idea raised by one of the attendees. They are held once per month and are invite only. The goal is to prepare people for future roles in leadership by tackling questions and problems that they will face in those roles. Brilliant idea, a huge +1 from me on this. Something we could do better at Atlassian I believe.

Conclusion

Culture Con was fantastic. You should definitely add it to your list to attend next year. I will be going back, without a doubt. To the organisers, thanks for having me. To the attendees, thanks for the gold!

JIRA 5.2 Webhooks with Twilio

November 10, 2012

JIRA + Zapier + Twilio = Happy Customers

JIRA 5.2 includes webhooks – the ability to update another application about the status of an issue in JIRA. I put together this Twilio blog on how to integrate JIRA and Twilio via Zapier. It is very cool.

Read it now >>

Events in November

November 3, 2012

Gosh, this is going to be a busy month!

SF Culture Con, November 7
Next week there is a special event hosted by the fine folks at Dyn Inc, Culture Con. I hear it was a huge success over in New Hampshire and now they are bringing it to SF city. Looking forward to it.

QCon SF, November 5 – 9
We’ve also got QCon on in San Francisco next week. Lots of excellent speakers. Highly recommended.

SF StartUP Product Talks, November 13
The following week we’re hosting another SF StartUP ProductTalks meetup at Atlassian. Ron Lichty is speaking, should be killer.

SF Agile Marketing, November 27
Finally, we will close out the month with SF Agile Marketing. Paul WIllard, CMO at Atlassian, will be speaking on Growth Hacking. One not to miss.

Come for one, or join them all, I hope to see you there.

Have a suggestion for another event that folks should get to this month? Tweet me and let me know.

Following up from my presentation on Saturday at the Rakuten Technology Conference 2012 in Tokyo I received some questions via email. I wanted to share them below in case anyone else had similar queries.

Does Atlassian measure whether ShipIt Days are profitable? Everyone knows “innovation” is important for a company. On the other hand, it’s hard to measure the effect.

Atlassian does not measure profitability of ShipIt Day projects. You are right, it is difficult to measure the effect!

Sometimes a ShipIt Day project is a feature of an existing product, other times it is a new internal tool to assist other Atlassians and reduce a bottleneck in delivering value to customers, and still other times it has nothing to do with Atlassian at all. For example, in years past time has been spent contributing to Asterix, an open source PABX that we use.

We do measure the impact ShipIt Days have by keeping track of how many of the project do ship to customers – that is, how many projects have delivered customer value? That is the best proxy for identifying the value gained from the ShipIt Day activity without trying to infer the profit contribution.

At the last ShipIt Day, #20, do all Atlassian employees attend the ShipIt Day? Or is it voluntary? Which do you think is better?

Not all Atlassians participate, although it is certainly encouraged.

People from Talent, Product Advocates, Product Management, Marketing, Support, Operations, System Administration, Internal Systems, Quality Assistance, and yes, Engineering participate. We now run ShipIt Days in our Sydney, San Francisco, Gdansk, and Amsterdam offices.

These days most ShipIt Day projects have a team of people so that they can achieve more in the short space of time. Plus, this means they can have a cross-functional team – product owner, tester, designer, developer, etc.

One thing that prevents everyone from participating in every event is the queue. Those in direct customer facing teams such as Support and Advocates can not just drop everything and participate in ShipIt Days. These teams have to manage their load and so often some people will participate in every second ShipIt Day. Otherwise they would risk our SLA (Service Level Agreement).

About “Shipped” stuffs (products, services), are they maintained? If customer report some bugs or ask to improve, does anyone respond to it? I think because the developer who made the stuff have their own work, so it’s difficult to make time for maintain that. How do you do that?

The short answer is that it depends.

Keep in mind that we are our own best customers – we are building for software teams, and we are a company of software teams. So when we get value from a ShipIt Day project there is a good chance the customer does too.

If a project is included into a future release of a product then it is certainly maintained. Occasionally ShipIt Day projects end up on the Atlassian Marketplace as an Unsupported and Open Source plugin that is infrequently, if ever, updated. Others may live on after ShipIt Day as a repository on atlassian.bitbucket.org - allowing a customer to take the code and do as they please.

Finally, if a team is really passionate about the project they may continue to work on it during their 20% time (subject to their colleagues buying in to the idea and approving future 20% days). In most cases the projects that provide customer value have a place on the roadmap as the Product Manager believes in it.

Regarding the user feedback part, you’ve utilized issue collector to get a lot of feedback from customers. I’m also familiar with the way of working like Lean Startup. But I’m wondering if the issue collector is sufficient to collect customers’ voice in detail. Don’t you think if you need separated interview-type activity, some proactive things?

We do have a separate customer interview process where team members will Skype customers or visit them on-site. We also conduct usability tests. Heck, we even have customers come into the office for lunch or a beer. The Issue Collector is just one part of a broader Customer Feedback program at Atlassian. And that program is constantly evolving.

One thing to note, the ability to get feedback from the end user and not simply the ‘gatekeeper’ that has an Atlassian account is a huge bonus that the Issue Collector provides.

Sometimes, even customers don’t know what they want, which implies that it might be risky to heavily depend on customers’ feedback, right? Do you have any special operation to come up with an idea from totally different point of view?

Spot on! Customers don’t know what they want.

We conduct paper prototyping to explore new ideas and validate those ideas with customers. It is a cheap way to get feedback. However, some customers can not visualise something unless they see it, and it is only then that they tell you it is once what they are looking for – after you have built it. For that reason we try to minimise the time/cost spent building until we have satisfactorily validated that we solved the customer problem.

Another thought, we have used Five Why’s to get to the root cause of a customer problem. That is a great place to start building a solution!

Regarding the innovation part, I think that the system you presented like awards, contests would definitely work well. But it doesn’t necessary mean that all the people like this way of working. So my question here is – how have you kept people’s motivation apart from such award or so? Is they any special tips or operation to do that?

There is a whole talk here on extrinsic vs intrinsic motivation. Dan Pink says pay people enough so that money is off the table. The other piece then is the intrinsic motivation, for which autonomy, mastery and purpose are key.

Autonomy – we’ve given Atlassians ShipIt Days and 20% time to allow them to be self-directed.

Mastery – there are constant opportunities for new challenges and for individuals to hone their skills. For example, once an Atlassian really gets good at something we’ll ask them to present on it at a conference (or they will get invited, thanks Rakuten!).

Purpose – why do they do what they do? To solve a customer problem. This is where the feedback is key, giving the feedback directly to the team reminds them of the purpose.

 

Like that? Follow me on Twitter for more on Agile and Innovation. If you have any questions feel free to tweet or add a comment below. Thanks.

Well I must say, Rakuten is an amazing company and I am very impressed. They certainly know how to put on a conference!

My favourite talk was from Taichi Watanabe who spoke about the 10% Rule at Rakuten Travel. I have asked him to share his presentation, it was gold.

I gave a talk on the agile and innovation programs we run at Atlassian. If you are interested take a look:


Some questions cropped up subsequent to the talk – read the Q&A now.