I’ve been scratching my head lately regarding management, and what is it good for. So I’m probably going to spend some time on the subject in this here blog. Long time readers of this blog (you poor guys, thanks for sticking with me!) know I’m a fan of Manager Tools. For the last seven years,
In my last post I wondered why Agile emerged in the software business, rather than in another field. I still wonder about this, but in the meantime, something happened that made me think that “we’re not the only ones”. The new field? Video games. And I’m not talking about the production side, which is obviously
I was reading Lior Friedman’s post about the agile research. He raises an interesting question: Why are agile studies coming from the exact science fields? After all, we don’t see groups of accountants doing a stand-up meeting every morning. The easy answer of course, that’s where they practiced mostly. We tend to look under the
Everyone likes to know the answer. In fact, this question can be interpreted in many ways, and answered that way too. For example, if we’re using agile techniques, we assume things will go wrong. So what we’re asking really is when is the scope going to be completed. And that’s not the way agile works,
I’m addicted to predictability. I admit it. I want my life to flow along, according to plan. Sure there will be some minimal changes, but I can adapt. I’ve given up on this long ago, as I came face-to-face with real life. I know life is not predictable. And I have embraced change, as agile
I’ll be presenting in the Israel .Net user group on unit testing with a star wars twist on May 22nd. So don’t be shy, learn Hebrew, if you don’t know already and register here: http://idndug-may-2012.eventbrite.com/ And if you haven’t checked out my latest article “The Developer-Tester Divide” , what’s your excuse? While you’re at
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
The CHAOS report says agile projects succeed three times more than non-agile, reports Mick Cohn. Good news, until I recalled that the CHAOS manifesto defines success as on budget, on time, and with all planned features. Show me an agile project that has all the original features in it, I dare you. Agility has change
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