In a previous post I told you had a plan to give a presentation in Paris, march 30th. It was for the first birthday of the French Scrum User Group. Here’s my feedback on this event.
I arrived in Paris around 4 p.m to avoid traffic jam, I was warmly welcomed by Xavier Warzee from Microsoft France. Microsoft was the sponsor of the evening and the event took place in their main offices in Paris. Xavier let me visit the place, all the offices, Tech-Rooms and let me “play” with the “Table-Surface”.
A few months ago, via a comment on our Scrum Video, i met Jim. He is teacher in University (North Carolina – USA) and asked me if we had a “copyright free” version of our Scrum Video. Indeed Red Hot Chili Peppers, music on our Scrum Video is blocked by youtube, for a copyright issue. After some emails, i learned that Jim was teaching Agile and Scrum courses at University in collaboration with one of IBM’s leaders for their use of Agile.
Personally i was very happy to learn that future consultants, project managers, developers,… can be so soon in touch with Agile techniques.
First of all I would like to apologize… I’m really sorry… for such a “buzz title” in this post ;-) Okay but, let’s see what’s beyond this “Scrum 2.0” expression.
In the project we worked 6 months using Scrum, the release was done and we had one month off. After the one month off, we were supposed to continue working on the same project with a second release in the next 6 months. Before starting, we took the opportunity for a lessons learned about our 6 first-months of work. One point was about the way we work in Scrum mode. Should we do exactly the same during the next 6 months ?
When i initiate a project, i regularly have this question from a team member. “Look, what specifically will be my role on this project ?”. And i always answer… “i don’t know”.
To make your project a success first point to consider is that the team (and so do you) must be “multi-tasks”. Indeed, on a Agile or Scrum project , do not expect to have a “job description” with the different actors (developer, analyst ,…) and the various tasks associated with these roles (the developer is responsible for code ,…). No, on a Scrum / Agile project we can summarize pragmatism by: “Project comes first”. If the project success requires you go and buy colourful post-it notes in a shop, then you do.
I’m for the moment working on a serie of posts. Theme will be: “Five keys to succeed in your Agile/Scrum projects”.
The idea is to suggest five principles which, if implemented, will greatly increase your chances of success on a project using Scrum or methods Agile. Those posts will be based on various sources (training, coaching, feedback, lessons learned) . You can also apply these principles on a waterfall project using Prince2 or PMI.
Articles will cover Scrum principles, Agile principles but also other things like coaching principles or NLP concepts.
> Integration of a search engine > Maps in full screen > Better visibility of icons on the map (homepage) > Integration of an interactive map concerning bike (Villo, bike shops, regional cycle routes, cycling points ,…) > Integration of an interactive map car (Cambio stations, parking information with real-time transit parking ,…) > Module Survey > Free Widget (space to advertise for a contest or other) > Development of the video feature > Adding online forms (Taxis)
So there it is, you’ve discovered Scrum! You’ve talked with other colleagues or friends, you read a lot of blog and articles. Your stuff is ready, you read books until you felt asleep. You have selected a project that you could … no … that you want to achieve using Scrum! You are so ready !