Editor’s Choice: Gathering Requirements for Migration Projects, Part 2

Magnifying Glass

Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email

Another in the “Editor’s Choice” posts series — those blog posts which have been linked to by other sites, and which are perennial favorites for people clicking through. 

A classic example: “Gathering Requirements for Migration Projects Part 2,” originally linked to on Scott Sehlhorst’s blog. This second in a series on software requirements gathering for legacy migrations discusses in detail a common enterprise software project: the replacement of a legacy system, and duplicating functionality in the new system that exists in an old system.

Joy Beatty wrote, “On Tuesday I began an overview of the processes behind gathering requirements for a migration project and how these activities differ from a system with new functionality. I began by talking about scope, understanding business needs and working with end users. Although these activities have a lot in common with the approach for a new system, there are some key differences that were uncovered. Today, I am going to finish the discussion by drilling into a couple of additional areas that differ significantly – discovering the end-to-end functionality and working with IT. …”

Continue the blog post here…

More To Explore

Three BA Mistakes to Avoid

We’ve all heard the quote, “What we have here is a failure to communicate.” Failure to communicate is the bane of the Business Analyst (BA). The BA has the responsibility

Marketing Automation or CRM – Which do I need?

Here at Blue Fish, we design and implement commerce-based solutions across a variety of industries and company sizes. In nearly all those solutions, our clients also have varying needs to