Episode 168: Agile 2019 (Un)bagging

The Agile Revolution Podcast

Craig and Renee are in Washington, DC at Agile 2019 and ahead of day one have some fun and decide to open up the swag bag after collecting the badges and see what is inside:

View original post 111 more words


Episode 142: Agile and SSLM at cPrime with Zubin Irani

The Agile Revolution Podcast

Craig sits down with Zubin Irani, the CEO of cPrime, at the Agile 2016 conference in Atlanta and chats about:

  • CPrime is the largest Atlassian implementer and platinum partner
  • Need to make sure that ALM products work with your process and support and enable it
  • One of the big gaps in the Coaching world is coaches are staying away from technology – we have to leverage technology
  • SSLM (Software Service Lifeycle Management) – Agile, DevOps and ALM initiatives are fragmented, they need to interact and have dependencies on each other
  • 5 big trends – Agile beyond development, DevOps is taking centre stage, every company is a software company, digital transformation and the talent crunch
  • Agile Hardware – how do you build hardware in a more iterative way, how do we think about hardware and software being built together, how do we think about different about hardware design to…

View original post 25 more words

Episode 137: The State of JIRA with Jake Brereton

The Agile Revolution Podcast

Craig sits down with Jake Brereton from Atlassian who is the Senior Product Marketing Manager of JIRA while roaming the product halls at Agile 2016 in Atlanta.

  • JIRA is no longer just JIRA, now people outside of software are using it – now JIRA Software (that includes JIRA Agile), JIRA Core (lightweight version of JIRA) and JIRA Service Desk
  • Over 70% of users were using JIRA Agile
  • JIRA has over 1,000 addons in the Atlassian Marketplace, some exciting work being done around analytics and data
  • Many organisations are starting to question whether they need to adhere to all of the practices and overheads – find the way that is most efficient and productive that works for you
  • The double-edged sword of how configurable and customisable JIRA is – improved onoboarding experience, test instance with demo data and an active online presence
  • Acquisition of Status Page
  • Launched JIRA Software Mobile and…

View original post 5 more words

Episode 113: GreenHopper Handyman Folio with JC Huet

The Agile Revolution Podcast

JCHuetCraig and Renee, sitting on the banks of the Potomac River on a sunny but slightly windy day at Agile 2015, they catchup with JC Huet, creator of GreenHopper (renamed to JIRA Agile and post-podcast now JIRA Software) and Tempo Folio:

  • Craig was apparently the first client of GreenHopper that was built in a basement, now JIRA Agile is the most popular JIRA add-on with over 500,000 users, used by more than 80% of JIRA users
  • the idea was to have a tool that brought bugs into software management
  • the name GreenHopper represented the Green company branding at the time, and Hopper was for cards hopping between columns
  • a shout out to our friend Nick Muldoon (who is now writing Atlassian plugins at Arijea)
  • Tempo Folio plugin is about supporting cost management, including time sheeting, estimation, forecasting and allocation
  • time and dedication and about three months is…

View original post 34 more words

Atlassian Bamboo 5.11 Delivers Continuous Integration At Scale

InfoQAtlassian, makers of development tools such as JIRA and Confluence, have just released version 5.11 of their continuous delivery tool Bamboo with a host of new features to help teams scale and collaborate. The key feature in this new release is the ability to scale from 100 to 250 elastic build agents.

Source: Atlassian Bamboo 5.11 Delivers Continuous Integration At Scale

The Value of Values

Talk of values came up recently, and Atlassian as always was held up as an inspiration. The video covers it all, but I have always admired their values:

  • Open Company, No Bullshit
  • Build with Heart and Balance
  • Don’t #@!% the Customer
  • Play, as a Team

Episode 64: Interstate 40 East with Nick Muldoon

The Agile Revolution Podcast

Nick-CraigOn a road trip to Agile 2013 from Dallas to Nashville, Craig chats to Nick Muldoon while cruising in a Chevy Equinox eastbound on Interstate 40 between Memphis and Nashville. Nick is an Agile Coach at Twitter and formerly the Product manager for GreenHopper at Atlassian and whilst doing 65 miles an hour they chat about:

View original post 91 more words

Episode 36: Revolution World Tour

The Agile Revolution Podcast

World TourCraig, Renee and Tony talk about Fed… no, Ship It! days, recent changes to Yammer and LinkedIn and the 10 agile bloggers you should know about. We also review Tony’s recent excursion to BA World and Renee’s journey to KLRAT and ponder just why Tony has such an obsession with pants…


View original post 73 more words

Episode 16: Motivated To Make Walls Fun

The Agile Revolution Podcast

WallWith Tony on assignment on an island, Craig and Renee talk about motivation, Renee makes a ballsy prediction about fun and we talk about dead walls, tools for walls and everything in between:


View original post 40 more words

Facilitating a Successful Developer Day

When an executive manager approached me a few weeks ago with the idea of running a developer day with one of his Java development teams, I jumped at the opportunity. The idea was simple: emulate the success of Google 20% time and the Atlassian Fedex day to improve the collaboration and skills of a bunch of developers.


I started out with some research and found the following excellent resources:

The Running Sheet

It was decided (in hindsight, a fantastic decision) to hold the day in a neutral venue away from the usual office in a training room environment. The pre-requisites equipment-wise were at least one machine per two attendees (we ended up with two high-spec developer machines and a bunch of laptops), network access, a projector and the usual agile materials of post-it notes and pens. A supply of snacks and drinks was also available to give it a “start-up” feel.

As we had two days and wanted to also allow for some presentations and discussions, the run of the days ended up as follows:

Day 1

9.00am: Standup Introductions (All), why are we here, team building exercise (paper folding exercise)

Give each member of the group an A4 piece of paper, the facilitator needs one too. Have them close their eyes. The facilitator issues the instructions and follows them as well. No questions are allowed.

  1. Fold the paper in half.
  2. Rip offf a corner
  3. Fold the paper in half
  4. Rip off a corner
  5. Fold the paper in half
  6. Rip off a corner

The group can now open their eyes and find that there are many different shapes of paper. The debrief covers the need for two way communication and that the different perceptions of the people caused the many different designs. If time permits the group can be put in pairs. Have the pairs sit back to back and repeat the exercise using two way communications and find that the patterns come out closer

10.00am: Presentation (Agile Tools & Maturity)

11.00am: Brainstorm / Retrospective: What would make this a better team -> how can we make a difference in 24 (8) hours

The idea was to review the good and not so good of the team and help determine the issues the team would like to tackle.

12.30pm: Iteration 0 / Planning / Lunch

Melbourne GI Developer Day Rules

2.00pm: Iteration 1

Including a quick planning session

3.30pm: Iteration 2

Including a quick retrospective and planning session

Day 2

9.00am: Standup

Overview of highlight of yesterday and what planned to do today.

9.30am: Iteration 3

Including a quick retrospective and planning session

10.30am Iteration 4

Including a quick retrospective and planning session

12.30pm: Developer Practices discussion / lunch

Based on the development practices prescribed on the Donkey open source project.

1.30pm: Iteration 5

Including a quick retrospective and planning session to ensure ready for the 3pm demo

3.00pm: Demo Showcase

Melbourne GI Developer Day Demo

4.00pm: Closing Statements and circle

The Outcome

Well, it turned out better than I could have imagined! Iteration 0 everybody turned a bunch of PC’s in boxes and chairs and tables into 5 distinct teams. Story walls went up, planning started and the software required was downloaded (or people remotely accessed their work machines). Pair programming naturally happened (the limited number of machines helped this) and teams supported other teams when they ran into problems or needed assistance.

Melbourne GI Developer Day

The 5 teams focussed either on stuff they wanted to learn or things they wanted to achieve to help their everyday work. The projects attempted roughly consisted of:

  • a mobile web application using the Play framework
  • investigation into using JMX for application monitoring
  • automating WebSphere environment creation with JACL / Jython scripts
  • scripting legacy mainframe account creation for testing purposes
  • performance testing using JMeter and The Grinder

The morale was high at the end of the two days, everybody clearly learnt something and the developers were asking when the next event was. Success!