Agile development a perfect fit for BW/4HANA migration
- Dónal Geraghty
- Oct 1, 2019
- 2 min read
“Agile software development (ASD) advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages rapid and flexible response to change.” (ASD Wiki)
The migration from BW to BW/4HANA is a complex task (whatever migration option is chosen) and certainly can’t be done as a “big bang” strategy.
Once you’ve executed the BW/4HANA pre-checker report on your system you can see the substantial effort required to convert object types to HANA compatible object types, ABAP code review and modification, manual BW design and build modifications (objects where no conversion tool is available) etc.
The following are the main features of Agile project management:
Iterative development cycles
Self-organizing teams
Multi-level planning
Dynamic scope
Frequent collaboration with customer and/or business sponsors
The practical approach to a BW/4HANA migration would be
Split the migration tasks into iterative development cycles
Have a dedicated BW/4HANA migration team
Have a high-level and detailed plan of each of the migration elements.
Item can be prioritised based on feedback from the business.
As you can see from the above features of agile project management sit perfectly for a BW/4HANA migration.
A substantial piece of the BW/4HANA migration is converting the classical BW objects to BW/4HANA compatible objects. For an in-place migration, once you convert an object in the development system, this can’t be changed until the object is converted through the landscape (including production). Only then can development can resume on this object.
So, for remote and shell migrations, it’s not mandatory (but recommended) to split the migration into iterative development cycles.
For In-Place it is essential to do this as if this is not done then you’re basically locking the landscape from future enhancements until all objects have been migrated from the development system all the way through to the production system which could be anywhere from a 3 to 6-month project (depending on the size of your BW system).
Two of the main principles underling the Agile Manifesto are:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
The splitting of BW dataflows into manageable sizes of work fit’s perfectly to these principles. For example, having an iteration/sprint for the conversion of 3 to 5 BW dataflows that potentially could be completed in a few weeks allows for delivery of work on time along with a satisfied customer!
To conclude, once you’ve decided to migrate your BW system to BW/4HANA system – a review of the Agile Software Development methodology should be undertaken to see if it’s a right fit for your BW/4HANA migration.
Dónal Geraghty operates SeaPark Consultancy. SeaPark offer bespoke SAP BW/4HANA migration support and solutions. We work with your existing on-site team & external vendors to optimise BI operating processes and ensure the highest levels of ROI.
Have we connected yet here on Linkedin?
Why not catch up with our library of blogs at https://www.seaparkconsultancy.com/blog-and-news
I liked how this article explained that moving a big BW system to BW/4HANA works best when you break the work into small steps and keep checking progress often, so the whole project doesn’t get stuck at once. Pay Someone to Do SEO Copywriting was something I once used when I was stuck on a long school write‑up and needed help making my sentences clear so others could follow my ideas more easily. Your post made me think that big tech changes feel more possible when you take them piece by piece.
I read the post about using agile methods to make a big tech migration like BW/4HANA easier to handle and it helped me understand why breaking big work into small steps works so well in real projects. When I once had to fix a long essay I turned to law paper proofreading and editing service because I was stuck and needed clearer ideas on how to fix my structure, and that made finishing feel less scary. Your piece reminded me that careful planning and steady progress help with both coding work and studying.
I read your post about agile development and BW4HANA migration and it made the ideas feel much easier to follow even for someone new to the topic. When I was swamped with online classes last semester I even had to pay someone to complete my online course so I could focus on big tasks like learning new development styles. Your article reminds me that good planning makes hard work feel lighter.
I read the post about how agile development fits BW/4HANA migration by breaking a complex SAP system move into smaller cycles and helping teams adapt plans often to avoid big bang work all at once, which is a smart way to handle difficult tech projects in real life. Back in school I relied on a time I had to pay someone to take my online Management class when a project felt too huge to handle alone, and learning to break things down was the key. That made the idea of using agile methods here feel very relatable and practical.
I read the article about how agile development breaks the big SAP BW to BW/4HANA migration into smaller cycles so teams can adapt plans often, focus on short wins, and avoid doing everything at once, which really helps with such a complex move. I thought about a time I really used this do my online exam help when I felt stuck on a big test and needed clear steps to finish it, just like agile breaking things down makes work easier. It makes me see that small steps and flexible planning can make big tasks feel less heavy. Your post had me smiling as I read it.