Conventional wisdom generally holds that the ratio of developers to analysts in an Agile framework is about 4:1 or 3:1. In essence, it says that 1 analyst can support the […]
Tag: requirements planning
Gathering Requirements in a Green Field
In my time at ArgonDigital, I’ve had a chance to work with a number of different clients, operating in a range of industries. Oftentimes, these clients begin projects with a […]
The Most Important Part of A User Story
The last couple of years has seen a wholesale shift in development methodologies among the Fortune 1000 companies from Waterfall to Agile. It is not an exaggeration to say that […]
Setting boundaries in Agile Requirements Management
I was once part of a team at a consumer-facing technology company, who described themselves as incredibly fast-paced, operating within a rapidly changing environment. This team was smaller (4 developers in a 10-person […]
Aligning User Expectations with Business Objectives
Projects with clearly defined business objectives can and do fail even if they deliver functionality that syncs closely with the business objectives defined for the project, but do not meet […]
Planning for Software Requirements – What’s Your Plan?
I was recently working with a customer and a number of their business analysts on a specific project, when I asked them what they did around planning for their elicitation […]
Requirements Webinar Downloads – “Tool vs. Process: Which Comes First?”
Joy Beatty, VP Research & Development at ArgonDigital, presented a requirements webinar September 21 hosted by eDev Technologies. The webinar is part of their Requirements Leadership Forum lecture series. Joy […]
Software Requirements Impact on Technical Debt – Part 2
This is the second part of a two part series on the impact of software requirements on technical debt. Part 1 defined technical debt, delved into its importance, discussed its […]
Software Requirements Impact on Technical Debt – Part 1
This is a two part series on the impact of software requirements on technical debt. Part 1 summarizes technical debt and part 2 discusses the impact that software requirements can […]
How to Shoot Yourself in the Foot: Conclusion
Conclusion to the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do instead.” […]
Work Harder, Not Smarter
I am all for great tools and processes that increase efficiency of work, facilitate better accuracy, allow for repeatable results, so on and so forth. But sometimes they simply do […]
Tips for Turning “Fluff” Requirements into Real Requirements
Tips for Turning “Fluff” Requirements into Real Requirements Lately I have been getting a lot of “fluff” requirements from my stakeholders… The system must be flexible. The system must allow […]