Question

Ruby on rails

In the agile approach to project management, the application is built incrementally. How do migrations

in Rails support an agile development approach?

Answer 1

Answer:-

In the agile approach to project management, the application is built incrementally. How do migrations:-

• If you do want to do Agile that's great. I would try and get someone who has done it before to help you through the process.

• People often ignore the refactoring step when they first try Agile. Do NOT. It will kill the project.

• Think in vertical slices (features) instead of layers. Implement vertical slices so you have a working system after the first feature card is done. Once it's working, keep it working and just add with each feature card.

• Basically, you review the existing system(s) and prioritize the new features or functionality that you will need to build to replace them. You execute these in priority order, checking your work against the end user base to confirm that you're both solving their existing problems and taking opportunities to solve other problems as they are uncovered. At some point, you'll have sufficient functionality in the new platform to either co-launch it or do an in-process swap over from the old to the new.

  I'd guess most systems would require 12-18 months for this to be mostly complete; more complex systems might take more time, and less complex systems might move faster.

• We've been using Agile on a project that entails moving from an old application to a new set of applications and a new architecture. Our situation is a little different in that we are trying to not only redo the existing application (used internally by our sales, finance, sourcing and warehouse departments), but we are trying to improve each department's experience along the way. One challenge that we've seen using agile is that the business value for moving parts of the functionality for a given business unit is high, but other parts is low. We therefore find ourselves making new applications and keeping the old application running while we transition. We are having trouble getting the business to see the value in concentrating on moving one "customer" to a completely new application. We are however getting a lot of high value stories into our sprints. I think soon we are going to come to a pint soon, when we have to convince the business that we need to focus on one unit at a time.

  So, to answer the original question, yes agile is a good way to go. Be prepared for some dependencies to crop up and guid some of the teams decisions along the way

in Rails support an agile development approach?:-

yes

The purpose of user stories is to meet the needs of real users so that each feature that is designed and developed delivers incremental value. It will increase the quality of your software. When the work is broken down into manageable units and frequent builds, testing and reviews are more focused.