Scrum – First Sprint
Lately i’ve been pretty excited about work. For the past month i have been a Scrum master in a team of 4 people (including 2 developers, Jose and Pepe and the Product Owner Silvia, who is also the project manager).
What is Scrum?
In a few words, Scrum is an Agile metholodogy for project management. It applies mainly on software engineering projects but is also suitable for other kind of projects. The main idea behind Scrum is to have small iterations of works, delivering a shippable product at the end of each one. The client is really involved in the project (via the Product Owner) and can give his feedback over the product very often and very early in the process. Priorities are decided by him and on each iteration, the team focus on developing the most important stories first, based on the 80/20 rule (80 % of the users will use 20% of the features, so those 20% features should ideally be developped first). Its advantanges compared to more classical approaches (Waterfall) are numerous: flexilibity, frequent and early feedback, prioritization of the scope, …
Scrum methodology
Product Owner
Silvia is the project manager, but for the Scrum needs, she took the role of the Product Owner. Our business situation is a bit complex and it is impossible to get the client involved and working along with us. So Silvia had the dream role of trying to get the client to share his thoughts with us, and it was far from being easy. The day after the beginning of the Sprint, the client finally gave us screenshots of the sites we were supposed to redevelop, … The other main role of Silvia, obviously, was to decide about the priorities of the features. Although at the end we are supposed to develop everything, it is important to focus first on the most important, and thats what she helped us to do by bringing a more business-oriented vision to our daily meetings.
Scrum master
As a Scrum master, i am in charge of keeping the project moving on and making sure that all the team is following Scrum processes and artifacts. I lead the daily meetings and make sure that we are still in phase with business priorities, while also trying to remove impediments from the team. I am not actually doing any development nor have any decision-making role, but i try to help and encourage team’s communication and keeping track of everything that is done and try to foresee what is coming next to give Silvia some vision.
It is my first experience as a Scrum master and only my second experience overall in a Scrum team. One week ago we actually closed our first iteration, and made a demo to Silvia and some stakeholders (3 of my superiors including my head of division).
To be honest, for all of us, this first Scrum experience was really made in a complicated context – most of the time not compatible with Scrum:
- even after beginning the first sprint, we kept adding tasks and changing the sprint, first because the requirements were not 100% complete yet, and second because everybody was discovering the platform so there was many unplanned elements to configure and/or implement,
- the development team is only made of 2 people, not cross-technical. They can’t really replace each other (one is more front-end oriented whereas the other one is more back-end oriented) and don’t work at the same hours and same places,
- we are literally spread all over the world. Jose is working with me in Madrid, Silvia is working from home near San Francisco and Pepe is based in Mexico,
- Internet connections were sometimes failing in Mexico.
But we made it and actually got a nice result, thanks to everybody’s work.
The main issues we had
We had a lot of issues during the Sprint. Some we could and should have anticipated more, some we seriously couldn’t do anything about:
- for both front and back-end, we were behind an internal framework for which there is little documentation and we barely received any training. Good thing Jose was here, cause he knew a lot, but Pepe obviously did struggle for some time on learning how to actually use the framework for the front-end part (being based in Mexico, he barely has any technical support since people using the framework are all in Madrid). He actually learned fast and improved some of the basic stuff that were made from Madrid!
- requirements and technical details of what was REALLY needed were sometimes coming or understood late,
- since we had only two developers, sometimes one for waiting for the other for some explanation or some piece of code logic to be available.
The BIG mistake
We actually started the Sprint without fixing an end date. Although it is one of the basic thing for a Sprint, we thought that just fixing the scope would be enough. BIG MISTAKE. After a while, we realized that we were not focusing anymore on having something deliverable and shippable to show at a given moment. Thats when we started worrying about priorities and really put apart some of the stories, although it was hard.
Despite this, we managed to bring fresh air to the logic and the front-end.
And we are now running the second sprint 
The tools
When doing Scrum, the best situation is when all the team is in the same room, with a big wall or a big whiteboard. People can draw a complete sprint backlog and a complete product backlog on the whiteboard, and physically moved stories (post-its) from one state to the other. The simple act of actually moving a story is usually a real plus in the process.
Unfortunately, due to our particular situation (4 people spread over 3 countries), the physical whiteboard would have been too complicated.
So we went for an Excel sheet, that i improved along the Sprint, basically saying for each story the remaining estimated time; and also gathering also information like the actual velocity of the team, the planned time (supposing people were able to produce 0,7 man day by day), …
We tried also Pivotal Tracker, but found some problems with retroactively doing a Sprint backlog, and with remaining estimations.
About the team communication, well most of it was done through email. Scrum meeting were held at 5pm (CET time), in a meeting room, using Skype for the calls and Webex to share my desktop. I would usually share the Excel backlog and directly input the info on it, live; as well as share the PDF documents or Firefox to read an email together!
And i think thats it… Other sprints are on their way so i’ll let you know about any relevant new info about Scrum or our use of Scrum!
Nicolas.
Gérer ses emails de manière productive.
Gérer sa boîte email est un vrai challenge lorsque l’on commence à travailler. La boîte perso, la boîte pro, les notifications des services sociaux… Ce sont des dizaines d’emails qui nous arrivent chaque heure et que l’on a pas toujours le temps de traiter.
Il y a quelques années, j’avais l’habitude de lire mes mails, et de remettre en « non lu » les mails que je n’avais pas eu le temps de traiter. Des règles de filtrage me permettaient de déplacer automatiquement certains mails vers des dossiers en particuliers, si bien que je pouvais avoir des mails non lu dans 5 dossiers différents.
Ce process semble simple, mais au final fait perdre du temps (les nouveaux mails arrivent dans plusieurs répertoires, qu’il faut donc vérifier tour à tour) et augmente un peu le stress. A chaque fois que vous ouvrez votre boite mail, vous vous rendez compte que des mails sont non lu dans plusieurs répertoires distincts, sans compter les mails fraîchement arrivés.
L’un des thèmes récurrents sur les sites de productivité (Zen Habits, …) est la gestion des emails; et après avoir parcouru plusieurs sites j’ai trouvé il y a deux ans la bonne solution à une gestion saine et productive de ma boîte email.
La technique
La voici:
- tous mes mails doivent au moins passer par la boîte de réception ( = la boîte principale), mais çà ne m’empêche pas d’avoir également des répertoires. C’est une manière de centraliser et de n’avoir qu’un seul point d’entrée.
- j’ai un dossier « TODO ».
- lorsqu’un nouveau mail arrive, soit je le traite immédiatement et je l’archive, soit je le traite plus tard. Par « traiter », j’entends transmettre, répondre, faire une recherche associée sur Internet, … Si je décide de traiter plus tard, le mail va dans « TODO ».
Aussi simple que çà.
Plus de stress en voyant « 23 messages non-lus »… Une fois tous les mails traités, ma boîte de réception est vide. Quelle sensation agréable …
Plus de perte de temps à relire un message déjà lu que vous aviez remis à non-lu, et « Ah oui c’est vrai celui-ci je peux y répondre que lorsque chose sera terminé, donc je vais le remettre en non-lu »
Tous les mails à traiter ultérieurement sont dans un et un seul répertoire. Une fois traités, vous pouvez les enlever du répertoire.
Concrètement, je ne viens que de vous parler de la gestion des emails proprement dit, mais quid de la fréquence d’ouverture de la boîte mail et des notifications? J’avais l’habitude d’utiliser GMail Notifier pour Mac et les notifications d’Outlook, puis me suis rendu compte que çà tuait ma productivité. Je pouvais être en train d’écrire un bout de code super compliqué, avoir une idée de génie, et soudain, une petite boîte s’affiche et me dit que j’ai un nouvel email. Evidemment, j’y vais, je regarde, peut-être je commence à le traiter, ce qui m’amène à naviguer sur Internet, et ainsi de suite… et bien sûr j’ai oublié mon idée de génie…
J’ai donc désactivé toutes les notifications. Et ma boîte mail est toujours fermée. Une fois toutes les demi heures ou heure, je vais l’ouvrir, je traite les nouveaux mails, ou je les mets dans TODO, et je sors. Je ne suis pas interrompu, ni stressé.
Pour résumer, donc:
- regarder ces mails à fréquence régulière, mais avoir la boîte fermée le reste du temps
- désactiver les notifications
- faire passer tous les mails par la boîte principale
- avoir un répertoire TODO.
GMail
Je ne saurais que trop vous conseiller l’utilisation de GMail, c’est ergonomique, user-friendly, la gestion des labels est très puissante et il s’intègre maintenant avec beaucoup de petits gadgets bien utiles (Google Calendar, Google Maps, Youtube, Google Talk, Google Docs, …). La Priority Inbox permet d’afficher plusieurs répertoires à la fois, pour ma part j’affiche la boîte de réception principale et le répertoire TODO. Je sais que les webmails se sont considérablement améliorés récemment (j’ai découvert il y a quelques jours que Hotmail a un chat integré à son webmail) mais pourtant je reste convaincu que GMail s’en sort très bien et son intégration avec d’autres services est tout bonnement imbattable.
Voilà, j’espère que ces conseils pourront vous être utiles. N’hésitez pas à me demander plus d’infos ou à partager votre propre expérience à ce sujet, çà m’intéresse : comment faites-VOUS pour gérer et trier vos emails?
Nicolas.
My homepage finally updated!
I have been talking about this for a long time, but recently i procrastinated a lot… Anyway, now it’s over, i’m done and i can proudly announce that the new version of my personal homepage is online!.
www.nicolasdaudin.com is now under PHP5. For you it’s a very slight change but for me its a gain of time in the content administration (now dynamic) and in the internationalization of my page. Plus i got to go over my basis in PHP.
I also took this opportunity to update the layout of my page, removing some items from the menu, to leave a clear menu leading to the most important: my blog, my personal profile and my profesional profile.
Updates are not over yet, especially in the content of these pages. Besides, i am thinking of adding a section concerning the design of web pages similar to mine… but i’ll let you know on that matter.
Anyway, feel free to go to my page have a look, and please give me your feedback, positive or negative.
Nicolas.
Google Chrome for Mac
Yesterday was (finally!) released Google Chrome for Mac.
I had heard about Chrome for some time now, but well, i have a Mac, and at work we are behind lots of security rules that prevent us to install anything. So i never really put my hands onto it. But finally, yesterday it came out.
Another Google tool to try out… and add to my collection of everyday Web apps? (GMail, Google Maps, Google Calendar, Google Reader, Google Analytics, …). Nothing sure yet.
Chrome
Let’s see.
Installation, all good. First launch, all good, all my bookmars and form entries are retrieved from Firefox, i connect to my Gmail, it seems to go a little bit faster. I try Twitter… and surprise, it cannot be accessed. But neither is it possible with Firefox, so…
I run some basic tests: counting the time to fully download a page, Chrome looks slightly faster. It is also less prone to failure and crashes: each tab runs in its own process, meaning that if one tab is blocked, you can just close the tab / kill the process. The other tabs won’t be affected. (so far, with IE or FF, if you have one problem on one tab, its the whole browser you have to close).
Google Chrome for Mac is still in beta. Extensions (plugins) are not available yet, althought i already saw plugins for del.icio.us, IETab, … Apparently, the bookmarks manager is not yet accessible, so you can’t really manage your bookmarks. But all in all, even though i’m missing my favorite plugins, i prefer Chrome.
The main reason is probably that i’m getting more and more Google-addicted… but soon enough we’ll talk about Google dependency.
Twitter… over capacity?!
Here is what i have since 15 minutes when i try to access directly my Twitter account (i.e. not using any Twitter apps) from Chrome or Firefox.
Twitter is over capacity
Interesting…
Soon enough we will know more about this!
