In our recent meet-up at the Agile Practitioner group, there was good talk about non-functional requirement testing. One of the first questions we discussed was how come non-functional requirements are second-class citizens. Usually they are patched on the app as an afterthought, and like any last effort, we botch it up. One of the answers
I’ve read an interesting article about how agile leaves security features off the hook. Security features are usually counted as a non-functional requirements. Non-functional requirements have been a thorn in the side of developers for years. But as with everything, it’s goes a bit deeper. Non-Functional requirements are hard to define. You can define uptime,
The more I put time into product management, since, that’s my day job, you know, I’m more aware of user experience. I’m talking about small features or behavior that if you ask any reasonable person, and by that I mean non-programmer, you’ll get a WTF look. Kevlin Henney shows this kind of photo, and now
This is the presentation I gave today at the “QA and Development in Agile” conference (It’s a bit more detailed than what the people in the room saw). This wasn’t a technical presentation, just an overview to the newly initiated to unit testing – third of the room wrote unit tests, the rest didn’t. And
I have a confession: I’m an early adopter. I like new shiny stuff. And if I like what I see, I’ll continue to use it. I was wondering a few days ago, what is the difference between what I’ll continue to use and what I’ll drop. The first tool that came to mind? Ask around
It’s been a few weeks now, for my tenure as product manager at Typemock. Time for a review. What did I learn of becoming the product owner in an agile company? Get yourself a good coach. That may be true for every profession, but especially for the newly initiated, it’s a blessing if you can
If you’re like most people you’re under-resourced. You have many more tasks than you can handle. Your team is fully booked. And the work keeps pouring in. They ask: “What should we do first?” What should we work on first to go into the product? Bugs coming in from support calls? Maybe this cool new