My company has been using an Agile approach to software development for over 8 years. We use a Scrum approach on our development teams. But here’s the thing: we don’t do everything that Agile Scrum is supposed to involve according to the experts. We’ve adapted the approach to fit our culture; specifically we have decided… Continue reading Are we missing something?
There’s a new page on this blog with info about some new directions I’m taking here. Check it out and let me know what you think. Enjoy!
Although I have talked about this topic before, I cannot write a series of blog posts about Agile planning without acknowledging one of the fundamental realities of software development that Agile so rightly embraces: sometimes your plans need to change. No matter how much time and effort you invest upfront trying to figure out requirements… Continue reading Incorporating new feedback
I will blog more about this soon but had to put it up as soon as I saw it. This is about Agile development at Spotify. I’ve got a link here to part 1 (of 2) but once you see the first part it gives you a link to the second. Maybe you’ve seen this… Continue reading An awesome and inspiring model
I spent some time today writing up goals for 2015 and for the next 5 years as part of my ‘end of year review’ for work. The goals flow from my performance review ending 2014 as well as from my reflections on what I would like to do and how I would like to grow… Continue reading Goals for 2015 and beyond
Way back in January I posted a plan to write about Agile planning (see the entry here: http://wp.me/p2BePD-3x). It was supposed to be a ten-part series that I hoped to complete in 3-4 months. The basic outline I wanted to cover in this set of posts was as follows: What’s so hard about Agile planning? The planning onion… Continue reading Regrouping on Agile planning
I started writing this blog a couple of years ago with the intention of posting once or twice a week. I wanted to share thoughts coming specifically out of my work as a product owner developing and selling software that enables users to manage their financial risks. I wanted to share things I was learning… Continue reading Update on what’s coming soon
In my last post I stated that the goal of Agile sprint planning is for the development team to know what pieces of working functionality – prioritized by the business – they can commit to delivering with relative certainty at the end of the two-week sprint. I also wrote that the keys to planning are… Continue reading Doing sprint planning well
So a couple of weeks ago I started a ten-post blog series on Agile planning with the following rough outline: What’s so hard about Agile planning? The planning onion (or is it a flame?) Listening to the market – outside in Product roadmaps When worlds collide: functionality that impacts across products Sprint planning: how much… Continue reading Listening to the market – outside in
I recently heard someone at my firm lodge the following complaint about Agile: ‘The trouble with developing software with Agile is that it tends to be very reactive as we build to satisfy the most recent requests; instead we need a more proactive and long-term approach to thinking about our software development priorities.’ To offer… Continue reading The Agile planning onion
InTruthItsNotThatSimple 