Skip to main content

Posts

Showing posts from March, 2009

First experiences on doing the SAP Scrum

In my blog on doing the SAP Scrum I described that we wanted to follow the Scrum approach for the second phase of the project. In the first phase we lived according to the traditional waterfall method and experienced the traditional issues. Now we are three weeks on route and this week we started our first realization iteration , our first sprint. The past three weeks we focused on delivering the product backlog , the scope in deliverables so to say. Scope that is to be realized with SAP BPM, SAP XI, SAP CRM, ABAP and some minor (*) web development. Now I would like to share some experiences that we gathered over the past three weeks. (*) Main focus is to realize backend components for an administrative process. The traditional process of writing all relevant documentation first is taking too much time. Writing business requirements – evaluate. Writing functional specifications – evaluate. Writing technical specifications – evaluate. Realize / Build. Test, if there is still time

SOA, after the hype

Oscar Mulders, a colleague, posted an article in Computable , a Dutch IT magazine. "Customers do not ask for SOA, they long for the expected business advantages" "Service orientation combined with BPM means shortening the throughput time and less effort required" You can read the whole article at the Computable site (In Dutch).

Interesting Twitter discussion

After my last post on doing the SAP Scrum at my current project an interesting discussion evolved on Twitter : Well I am a bit flattered that @yojibee thought that I was an SAP employee ;-) With " Doing the SAP Scrum " I was only looking for a catching title.

Doing the SAP Scrum

Today I finally finished my blog on the SAP Scrum. We started the second phase of the project by doing things differently, not the traditional waterfall but doing a Scrum . In this blog you can read about some thoughts that kept me awake: Why is it so hard to deal with changing requirements? Why is time pressure in a project forwarded to teams that are last in line, like developers and testers? Read more in SAP Scrum: An agile approach to deliver what is really required .