The software development process for most companies has a flow – gather requirements, design, implement, test, release. There can be feedback loops, iterative cycles, spirals or waterfalls, but they all have these steps. When teams “freeze the code” and submit to test, they are creating their own mini-ice age and dooming themselves to extinction.
Requirements / Slightly off-topic
Posted on:
Second-Mover Opportunities: Bringing a Gun To a Knife Fight
The main point of Laura’s article is the importance of engaging users to find out what they really care about. In this post we are going to pick up on another point she makes indirectly.
Laura also points out indirectly that the inclination of companies is all too often to build software that looks good on paper instead of software that is good in practice. A sort of rat-race of me-too’s and copycatting. Companies that add features solely because the competition has them are in for trouble.
Prioritization / Process Improvement / Requirements / Software development / Software requirements specification
Posted on:
Prioritizing Software Requirements – Kano Take Two
In our previous post on Kano requirements classification, we introduced the concepts and showed how to apply them. One of our readers commented privately that we didn’t show how to use the techniques for prioritization. We’ll do that in this post.
Requirements / Requirements gathering / Slightly off-topic
Posted on:
Dilbert gathers requirements
Another great Dilbert – http://dilbert.com/strips/comic/2006-02-26/ I won’t show the cartoon here, but here’s a quote from the first two panels: Pointy-haired boss: Why is your project four months behind? Dilbert: I still don’t have the user’s requirements because she’s a complete nut-job. […] This cartoon does point out the critical […]
Prioritization / Process Improvement / Requirements / Software development / Software requirements specification
Posted on:
Prioritizing Software Requirements With Kano Analysis
We’ve talked before about three ways to prioritize software requirements. We’ve also talked about incorporating risk analysis into ROI calculations for requirements. In this post we will look at how Kano analysis can be applied to prioritizing requirements.
Definitions / Project Management / ROI
Posted on:
Definition of opportunity cost
Why won’t my boss approve my project? I’ve done the math – it’s a good investment. Because it isn’t good enough. We learn the math and rationale behind these decisions in this article.
Slightly off-topic
Posted on:
What do you hate?
What do you hate about Tyner Blain’s blog? ack/nak posted a great idea – ask customers what they hate about you. Seth Godin has a book – Permission Marketing: Turning Strangers into Friends and Friends into Customers, and in his free ebook, Flipping the Funnel, he expands on what he […]
Process Improvement / Reviews / Software development / Software Reviews
Posted on:
OnTime Bug tracking software – $5 (or free) from Axosoft
Seriously.
There’s a crazy deal being offered by Axosoft. Buy a 5-user version of their $500 software suite for $5, but the offer expires February 24th. The link to buy the software is here – and only available on blogs. Axosoft is trying a social marketing experiment to see if they can promote their products and brand via the blog universe. It isn’t clear at what hour the offer expires, so you might want to get it on the 23rd.
Software development / Test Automation / Testing
Posted on:
Measuring the Cost of Quality: Software Testing Series
Should we test our software? Should we test it more?
The answer to the first question is almost invariably yes. The answer to the second question is usually “I don’t know.”
We write a lot about the importance of testing. We have several other posts in our series on software testing. How do we know when we should do more automated testing?