If it’s Monday this must be Chicago
Hi from the (other) Windy City. I have had the weekend to recover from the travel shock (AKA jetlag) and see some of this great city. Chicago is a really beautiful city – fascinating architecture and very friendly people.
To work you say – we don’t want to hear about your travels!
Day one of the Agile 2009 conference was great. I attended two sessions:
Workflow is Orthoginal to Schedule by…
“Agile” Is much more than a software development process
I’m not at all sure that I know what Agile / Agility is. I think it has its roots in software development approaches including Extreme Programming, which I think I first heard about more than a decade ago. Does anyone remember the even older RAD or RIP or JAD from the 1980s? The idea, then, was to use a collaborative, non-bureaucratic, approach to quickly produce software that was seen a…
How do your requirements smell?
While delivering the Business Systems Analysis course today one of the participants asked about the FRUEMP acronym (ISO standard 9126: Functionality, Reliability, Usability, Efficency, Maintainability, Portability) for requirements types – he suggested PERFUMe instead, which brings to mind the smell of a system.
It has been my experience on many projects that the NFR’…
Changes to the Business Analyst role
With the rise in the take-up of the Agile approaches, one of the most common areas of confusion is the changing role of the business analyst.
I feel that the fundamental nature of the role doesn’t change – ensuring the customer voice is heard and business value is protected. The the way we do analysis, and when we do the detailed analysis does change – focusing on”just-enough, just-in-time”…
High performance teams emerge
Something that came across to me last week when delivering a suite of Agile courses is how high-performance teams emerge. One day of the course covers the identification of requirements as stories; to help make it real we used two actual projects that the customer is about to start. They are the two most important pieces of work this group is currently facing, so the pressure is real.
Common testing issues
What are the key things that we find are issues for software testing? How can we address these problems? In my experience we usually have a solution to most of the problems – we just need to identify the problems and then we can workshop the solutions!
Here is my top 10 problems:1. late delivery of code2. poor requirements3. wrong requirements4. late engagement of the testers5. shoddy code6…