One of the most difficult tasks on any project is prioritizing requirements. This is because there is almost always disagreement about what the priorities should
Any business analyst who uses a computer can create a process flow. They have the tools. They know what a process flow is. So creating
The one thing that has been consistent on almost every project I’ve worked on is how easy it is to lose sight of the business
Many benefits of using a requirements management tool don’t become obvious until you actually use one. On a recent project, we used Microsoft’s Team Foundation
If you’ve read any posts in this blog, you’ve probably already picked up that visual models provide many benefits to any requirements elicitation and documentation
A nice trick that business analysts can use now that collaboration technology like Google Docs exists is to allow meeting participants to simultaneously collaborate on
It isn’t news that most business analysts don’t have enough time. Especially senior resources, who are loaded up with work because they are the only ones in
Everybody fears being wrong. They fear that they’ll be embarrassed, or that people will look down on them. They fear that they will be given
Often, business analysts see visual models as a discrete part of the requirements process. At some point they’ll create the visual models, and then they
Can a software requirements model help you determine if your project should be cancelled? The short answer is “yes.” By using ArgonDigital’s Business Objectives Model,
I hate the common phrase “expect the unexpected”. It makes me angry when I hear it, because it defies basic logic. If something is unexpected,
When is a software development project successful? Is it when funding is approved for the project? No, because that’s a first step, but nothing has
Generate and convert leads, increase revenue through ecommerce, and cut costs by automating operations.