Tag: requirements planning

Ratio of Developers to Analysts in Agile

Ratio of Developers to Analysts in Agile ArgonDigital - enterprise automation experts

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 work of 3 or 4 full time developers working on a project. For Waterfall projects, this ratio is higher and typically in the range of […]

Gathering Requirements in a Green Field

Gathering Requirements in a Green Field ArgonDigital - enterprise automation experts

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 number of legacy systems that need updated or integrated with; it is a rare opportunity for a project team to get to create a solution […]

The Most Important Part of A User Story

The Most Important Part of A User Story ArgonDigital - enterprise automation experts

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 the Agile revolution that has been brewing in small companies, startups and web companies for the last decade and a half has finally arrived in […]

Setting boundaries in Agile Requirements Management

Setting boundaries in Agile Requirements Management ArgonDigital - enterprise automation experts

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 business unit), so I expected the ability to get things done quickly to be one of our strengths. Upon joining, I was surprised to hear […]

Aligning User Expectations with Business Objectives

Aligning User Expectations with Business Objectives ArgonDigital - enterprise automation experts

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 user expectations. This may seem counter intuitive at first blush since the primary purpose of any enterprise software development effort is to deliver tangible financial […]

Planning for Software Requirements – What’s Your Plan?

Planning for Software Requirements – What’s Your Plan? ArgonDigital - enterprise automation experts

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 efforts.  Imagine my surprise when they said, “Nothing, that is what the project manager does.”  I probed a bit deeper, hoping that they did something […]

Requirements Webinar Downloads – “Tool vs. Process: Which Comes First?”

Requirements Webinar Downloads – “Tool vs. Process: Which Comes First?” ArgonDigital - enterprise automation experts

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 spoke to more than 220 people, comparing the reasons to start with the requirements process with why you might start with the requirements tool, and […]

Software Requirements Impact on Technical Debt – Part 2

Software Requirements Impact on Technical Debt – Part 2 ArgonDigital - enterprise automation experts

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 symptoms and summarized some strategies for paying it down. Part 2 discusses the specific impact that software requirements can have on technical debt. Brief Summary […]

Software Requirements Impact on Technical Debt – Part 1

Software Requirements Impact on Technical Debt – Part 1 ArgonDigital - enterprise automation experts

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 have on technical debt.  What is Technical Debt? Ward Cunningham coined the term Technical Debt in a 1992 OOPSLA experience report on his work on […]

How to Shoot Yourself in the Foot: Conclusion

How to Shoot Yourself in the Foot: Conclusion ArgonDigital - enterprise automation experts

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.” Short-change Time Spent on Software Requirements or Don’t do Them at All Don’t Listen to Your Customer’s Needs Don’t use Models Use Weasel Words Don’t […]

Tips for Turning “Fluff” Requirements into Real Requirements

Tips for Turning “Fluff” Requirements into Real Requirements ArgonDigital - enterprise automation experts

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 for multivariate (A/B) testing.   The system must be more user-friendly.   The features should be re-useable.   These all sound great in a power point presentation, but […]