Skip to main content

SDN Virtual Community Day

Last Thursday was my first webcast at SDN: Agile SAP, Mission Impossible? The replay is, just as the other sessions, available on SDN.
With a webcast it is a kind of difficult to interact with the people that are connected. Known pitfall is then to start talking faster and faster. I sure hope that the message got through. And for those who want to view the presentation again - it is available via SlideShare:


On the last slide some interesting links to more information are available.

During the session some questions arose in the chat window.
  • Use cases instead of user stories: We thought that user stories are very well applicable to web environments. But in our situation we also had a lot of backend functionality and processes to be realized. Therefore we decided to model everything with use cases.
  • Bigger size teams (>=100): Our team developed 1/3 of the total solution. The other teams did not work according to scrum. But if they did there is a scrum of scrums approach to share the information of all the scrum teams. Dagfinn Parnas: "scrum does scale very well, but it does require some extra thought with regards to organization, tools etc. Craig Larman has a few good books on the topic.
  • Using Scrum with non collocated teams: We were all located together, one of the biggest advantages for the project to minimize communication issues. So no experience yet. With online dashboards and nowadays conference call possibilities it can be made a success. As long as you keep to the basics of the approach: Working together during all phases of a sprint. I am curious to hear on experiences using Scrum and an offshore team.
  • How did the SAP team work together? An ABAP developer will not do CRM customizing. That's for sure. But everybody can help designing the solution, documenting and testing it. All team members are expected to help each other. We saw some pair programming activities during the project: CRM and ABAP consultant working together.
  • Resourcing scrum team: A project running at high speed needs a team that is almost 100% available. If not, people will miss a lot and have to catch up every time when they are back. Make sure that people that enter the team somewhere during the project that they get a proper introduction on how business is done within the scrum team.
Best advice according to Harald Reiter: Go out and do it!

Thanks to those who were attending my session. Feel free to share your thoughts on this topic with me.

Comments

Popular posts from this blog

SAP Fiori and SAP Screen Personas finally free for SAP customers

This week the SAPPHIRENOW event takes place in Orlando, a yearly event where SAP announces its strategy and new products. On Tuesday Bill McDermott, the CEO from SAP, did some major announcements . All with regard to making SAP simpler. In this blog I will describe the license changes for SAP Fiori and SAP Screen Personas. These new UI innovations are now part of SAP’s maintenance fee. SAPPHIRENOW keynote

Thank you @CiberNL and hello @TheNextView

Another strange moment in my professional life, I will leave Ciber to join The Next View  March 1st. Time to have a short retrospective . Team picture at outing 2010 First of all I am proud , proud on our SAP NetWeaver team: Alice, Arnaut, Bernard, Dave, Dennis, Frank, Guido, Harrie, Iemke, Igor, Jeroen, Juan-Jose, Laurens, Leo, Marc, Michael, Ravi, Roel, Ronan, Sanket, Steven, Ted, Tim, Wim and Vladimir. 

SAP TechEd 2013, the best and strangest experience ever

SAP TechEd 2013 - The best but also the strangest SAP TechEd ever Together with 10 colleagues I visited SAP TechEd in November 2013. Tim Burchartz - Jaap van de Mheen - Frank Hammen - Michael Hardenbol - Steven Spronk Twan van den Broek - Roel van den Berge - Ted Castelijns - Maarten Kreijveld (Missing on the pic: Leo van Hengel and Wim Snoep, who attended one day due to busy customer schedule) Best Team CloudSitter won the SAP InnoJam on Monday with an app that monitors new born baby’s on their wellbeing. Premature babies have an higher risk on Sudden Infant Death Syndrome , that’s why we came up with a sensor that tracks heartbeat, temperature and breathing. Information is stored in a central database in which thresholds can be validated. If there is reason to warn, the mobile app sends an alarm and changes color. Time to check upon your child. Matt presenting at InnoJam. Winning InnoJam meant that we could also participate in DemoJam , the ultimate stage for