September is the time for Scrum & Agile in Belgium to come back !
Maybe you have notice that this Blog woke up end of august after some months of inactivities. Here we go again, i have some posts almost ready to publish.
Some brand news also regarding…me. I relaunch my coaching and training activities. You will find a brand new page on this subject here: Coaching & Training. This topic will give you more concrete on my services. I’ve also updated my Contact page. If you want to work with me, well i’m available.
You’re facing a problem ? Having some (many) constraints ? Good for you ! You have the opportunity to be creative. Before that there is for sure a mandatory step. Grumble a little bit, Curse the whole world asking him ‘Why me” and “Shoot twice in the garbage” .:-) Ok now, calm down and let’s go further with this problem.
On my actual project I’m in the “Scope Definition” step. My difficulties are: I have a lot of stakeholders and a lot of input documents. And neither my documents, neither my stakeholders speak the same “language”. I mean vocabulary is always different.
March 19, I was in Toulouse France for the Agile SigmaT13 conference. Goal of SigmaT is to develop an Agile community in the “South-West” part of France. To do so, they make different actions, promotion meetings and conferences.
This conference was indeed a very nice experience for me.
14.30 I arrived at the university of Toulouse. My mission find my contact Claude Aubry. Claude was there, show me the place and invite me to meet the IceScrum Team.
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.