Comments on: Our Agile Journey: Next Steps http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/ Lessons we're learning about business, life & art in our software development company Wed, 08 Feb 2012 11:52:08 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Core Value #2 = Relentless Improvement | Behind the Scenes at Global-Roam http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-2269 Core Value #2 = Relentless Improvement | Behind the Scenes at Global-Roam Sun, 21 Mar 2010 11:02:42 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-2269 [...] We followed with a more intensive Autopsy 2 process. (c) [...] We followed with a more intensive Autopsy 2 process. (c)

]]> By: JIRA rewrite | Behind the Scenes at Global-Roam http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-2038 JIRA rewrite | Behind the Scenes at Global-Roam Fri, 05 Mar 2010 00:02:01 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-2038 [...] alluded to in Adam’s recent post on the next steps in our Agile journey we have taken the liberty of reorganising our JIRA workflow to better suit our new practices. We [...] [...] alluded to in Adam’s recent post on the next steps in our Agile journey we have taken the liberty of reorganising our JIRA workflow to better suit our new practices. We [...]

]]> By: Paul McArdle http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-1889 Paul McArdle Wed, 24 Feb 2010 03:35:24 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-1889 Hi Adrian, We will endeavour to post more regular updates on the blog with respect to progress (i.e. not just me). One of our challenges in moving to agile (and, in more general terms, being more innovative) has been the need to change the mindset internally whereby all of our team members are more active, and open, in sharing our successes and "learning experiences" with a broader audience. I am a firm believer in the value of <b>openness</b> - it is one of Four Core Values in the organisation (more about this later) that can be summed up with the philosophy = <blockquote> Unless we have a compelling reason not to, we will be open (internally and externally) in communicating where we are at, and where we are headed. We believe that this will deliver us more upside benefits than downside dis-benefits. This blog (or blicki?) is slightly unconventional, but part of the way in which we choose to do that. </blockquote> Hopefully the posts made this week by a few people is a sign that that mindset is changing! Stay plugged in for further updates. Cheers Paul Hi Adrian,

We will endeavour to post more regular updates on the blog with respect to progress (i.e. not just me).

One of our challenges in moving to agile (and, in more general terms, being more innovative) has been the need to change the mindset internally whereby all of our team members are more active, and open, in sharing our successes and “learning experiences” with a broader audience.

I am a firm believer in the value of openness - it is one of Four Core Values in the organisation (more about this later) that can be summed up with the philosophy =

Unless we have a compelling reason not to, we will be open (internally and externally) in communicating where we are at, and where we are headed.

We believe that this will deliver us more upside benefits than downside dis-benefits.

This blog (or blicki?) is slightly unconventional, but part of the way in which we choose to do that.

Hopefully the posts made this week by a few people is a sign that that mindset is changing!

Stay plugged in for further updates.

Cheers

Paul

]]> By: adriang http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-1882 adriang Tue, 23 Feb 2010 22:46:20 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-1882 Awesome progress! Following on from the comments from Chris, I've experienced using 'trio programming' to change minimise the interruptions and to try and keep a handle on productivity and it worked really well. Whiteboards...don't think I could live without them! So important for effective comms.... Do keep us posted on progress and what refinement steps you take on the way through! Awesome progress!

Following on from the comments from Chris, I’ve experienced using ‘trio programming’ to change minimise the interruptions and to try and keep a handle on productivity and it worked really well.

Whiteboards…don’t think I could live without them! So important for effective comms….

Do keep us posted on progress and what refinement steps you take on the way through!

]]> By: Chris Doyle http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-1866 Chris Doyle Tue, 23 Feb 2010 03:16:31 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-1866 Thanks Stephen. I have found there is always some theoretical resistance to agile implementation, but as soon as people start to do it, they see the benefit rapidly, and get - dare I say it - enthusiastic! Thanks Stephen. I have found there is always some theoretical resistance to agile implementation, but as soon as people start to do it, they see the benefit rapidly, and get - dare I say it - enthusiastic!

]]> By: Stephen http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-1861 Stephen Mon, 22 Feb 2010 23:56:19 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-1861 Hi Chris, I have found that pair programming is something that people have a natural resistance to as an idea (oh no, it will take twice as long to develop something!) when in reality it is the most natural development practice. Any time that you have looked over someone's shoulder to help them code is a basic form of pairing. Like any practice, pairing is something you should use intelligently. In my experience it is not appropriate for everything. It is, however, incredibly important in some situations, like refactoring critical, messy code. And yes, I love my whiteboard :) -Stephen Hi Chris,

I have found that pair programming is something that people have a natural resistance to as an idea (oh no, it will take twice as long to develop something!) when in reality it is the most natural development practice. Any time that you have looked over someone’s shoulder to help them code is a basic form of pairing.

Like any practice, pairing is something you should use intelligently. In my experience it is not appropriate for everything. It is, however, incredibly important in some situations, like refactoring critical, messy code.

And yes, I love my whiteboard :)

-Stephen

]]> By: Paul McArdle http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-1853 Paul McArdle Mon, 22 Feb 2010 11:23:17 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-1853 Thanks guys, These are some good next steps. Whilst the details may not be 100% correct, it is far more important that we keep moving, and refine as we go. Paul Thanks guys,

These are some good next steps.

Whilst the details may not be 100% correct, it is far more important that we keep moving, and refine as we go.

Paul

]]> By: Chris Doyle http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/comment-page-1/#comment-1848 Chris Doyle Mon, 22 Feb 2010 07:42:51 +0000 http://blog.global-roam.com/index.php/2010/02/our-agile-journey-next-steps/#comment-1848 All eminently sensible, I'm particularly interested to hear how pair programming works for you. While it has a set of benefits, the particular extra I can see in a small team would be the knowledge transfer, as this is an important risk minimiser. I was considering the role of single product managers and coders and the ways to get them to interact better myself as part of my thinking/planning, as it's critical to a team (on a regular improvement track) to have solid communication and knowledge sharing processes. All the iteration revisions should improve communication and really get everyone interested in the releases in each cycle - running solo iterations is more effective than standard waterfall development but is still isolating, and there's always a little buzz in the air when showcasing the latest version - particularly when you've developed a nifty new feature. Whiteboards - we don't have whiteboards here... they are missed! Look forward to hearing your progress. All eminently sensible, I’m particularly interested to hear how pair programming works for you. While it has a set of benefits, the particular extra I can see in a small team would be the knowledge transfer, as this is an important risk minimiser. I was considering the role of single product managers and coders and the ways to get them to interact better myself as part of my thinking/planning, as it’s critical to a team (on a regular improvement track) to have solid communication and knowledge sharing processes.

All the iteration revisions should improve communication and really get everyone interested in the releases in each cycle - running solo iterations is more effective than standard waterfall development but is still isolating, and there’s always a little buzz in the air when showcasing the latest version - particularly when you’ve developed a nifty new feature.

Whiteboards - we don’t have whiteboards here… they are missed!

Look forward to hearing your progress.

]]>