This is really the moment for me to pen down my thoughts on what it means to me and teams I work with to make NW . Yes the much awaited release mail has come from the program product team from Germany. This is the best news I have ever heard throughout the year about this topic of Netweaver. Today it is a Pooja to Goddess Saraswati and we are supposed to lay down our books, gadgets etc., and pray so we get to learn and explore the knowledge areas from tomorrow and for rest of years to come. As my latest blog was in May 2015, so at this moment I can’t stop exploring my knowledge gain in the year went by and it says without going I have to share that all. Yes exactly an year ago my area product owner came up a “tiny” backlog of exploring a new language version installation with a SAP Netweaver. So sat down and split that into still thinner pieces and with feedback from many quality experts in the java server area on how could we help evaluate a new language version compatible SAP NW stack. This all was evaluated in an existing maintenance landscape. While on the job, the Quality program accountable head and his aide senior project lead came up with enhancing this backlog to a yet another smaller system to evaluate if all works with a full fledged SAP NW JAVA stack against a “code” developed based on the a older code line. This is all around Q1 2015, when I was noticed I started planning for the backlog on backlog as still you know how that “tiny” backlog may look like later. As the evaluation of stack from our view was on older code line so it won’t be eligible for a word “Development” in the testing parlance, this is what started even from our senior vice president to vice president to managers and test project leads, support pack leads and managers considered a mundane backlog. This one was exactly yielding me minimum a mail to 100 in my inbox for the milestones’ we are in different support pack stages in the last 365 days. Yes there was not a day without an email about a clarification to me and my system, basis, stack, test teams. In spite of that I was also reading the news around me, sample was at . Then it was getting clear to me that everyone wants to be involved in the big party one day as there was not a day in our teams none want to say no or want to be grabbing a code and deploying or watching for a build.
To continue momentum, we were having calls daily, weekly and recurring and even an hour based check based on the internal milestones plan on what is the correct build, when to start deployment who to deliver the systems and who is going to crash it again in the name of development or testing the configuration on top of the JAVA stack we deliver . Then there were backlogs evaluating each Netweaver “Usage type” with a different Operating systems and different databases. Still with all these just handled as “adhoc” with nil planning effort and still every day dawn with a new planning for me and the teams around me. Then we are realizing now we could do all this “MANUALLY” without automation on our portfolio for the various combinations of OS+DB+SAP NW.
But stop why all these when manual communication, co-ordination, delivery process have all to do in an era of continuous delivery & integration, dev ops, cloud delivery model where we want to automate everything in an internet of thingy world? Every day I think this may be what our management strategy that we have to automate some part of that “delivery pipeline” and but not sure how to start. So the cloud and digital world is pumping me with enough automation tools all for all those communication and knowledge areas, and of course the deployments going to be automated with a “self-service”.. lot of work to do and need to plan…you know today I should not read much as it is a Pooja to Goddess Saraswati