Agile business analysts might manage a product backlog instead of requirements or write user stories instead of use cases. Agile teams depend on BAs for clear expectations of what \"done\" means and BAs often find themselves in the agile product owner role.
Is there value in keeping system documentation up-do-date? Keeping system documentation up-to-date is a challenge faced by many business analysts. In discussion forums, it is common for this concern to be raised in questions such as, “How do you avoid the problem of having only one or two BAs with full understanding and latest information [...]
Reader Question: “On my current project, I am getting my first exposure to User Stories. (As a..I want..So that.) With so many stories, I am wondering about managing them so that future analysts will a body of documentation to reference. Right now, we have no structure, so the list of stories grows with no real [...]
In my previous article I described my first ever agile project as a Java developer. I highlighted some of the challenges that we faced in terms of the requirements gathering and analysis work. In this article I’m going to talk about my first agile project as a business analyst, and how I took on some [...]
In my previous article titled “How I became an agile business analyst” I talked about my passage from the world of good old fashioned ‘write it all up and get it signed off’ business analysis into the uncharted territories of agile. In this article I’m going to describe my first experience on an agile project. I [...]
Hi there. My name is Tony. I live in Leeds, England and I’m an Agile Business Analyst. Oh dear, that sounds more like a confession at an Alcoholics Anonymous meeting than my first ever online article. It’s also not true and, so some people say, an oxymoron. Actually, what I really am is a regular [...]
Do you demand that your documentation serve double duty as a technical specification and a system document? While in the past I’ve done exactly that, my recent forays into more agile practices forced me to split how I see the value in various pieces of documentation. Adriana has already shared her views on how BAs [...]
As you read the title of this article, you may be thinking, “doesn’t agile methodologies emphasize verbal rather than written communication? is there any value in even talking about documentation in this type of project?”. The answer is yes to both questions. Agile developers may require very little written documentation to do their work, but [...]
When I first started working on an agile team, one of the habits I needed to develop was grooming the product backlog. In an agile environment my week-to-week and day-to-day focus quickly became more integrated with what the development team was working on each sprint. If I went into a sprint planning session without a [...]
John Simpson is director of customer outreach and marketing at Jama Software. John is a contributor for Business Analyst Times. At Jama, he represents the voice of the customer in their product strategy and communications. He has over 14 years experience working at software technology companies including Microsoft, WebTrends and Omniture. In his spare time, [...]
Agile teams typically differentiate between “epics” and “user stories”. In most cases epics are just really large stories that sit far down on your product backlog until the team is ready to flesh them out into more detail. The logical question is how to scope an epic and then break it up into user stories [...]