Affichage des articles dont le libellé est Scrum. Afficher tous les articles
Affichage des articles dont le libellé est Scrum. Afficher tous les articles

lundi 18 novembre 2013

El Scrum, dos años después

scrum1

They are almost two years that haploids chose the SCRUM methodology for all your projects.

Here is a small feedback seen by each of the key functions of the SCRUM: developer, Tester and Scrum Master, product owner

My role as owner of the product is reduced to understand the customer's need, the goal is to reflect the highest expectations and above all its ambitions. Regularly receive the specifications of several tens of pages for a mobile application, after having read the first 20 pages, it has already forgotten the first feature.

A specification does not weigh each characteristic according to their contribution 'business', i.e. do functionality generate revenue more in my application?

The method SCRUM to exploit this specification in "user stories" to assess the complexity of the preparation and the value for the business. This step is an excellent way to understand our customer that all functions are not worth and is crucial to the more 'important' to be developed against the current.

The other advantage of the SCRUM is the frequent delivery of the product, at each end of the sprint, our client is able to test and validate the implemented "user stories". This prevents unpleasant surprises related to the "development tunnel.

These frequent interactions bring confidence and work together throughout the project. All customers who were able to adapt this methodology (the availability of meetings well sprint, participation in the newspaper) enjoyed this equipment vis-à-vis transparency.

logo

Use IceScrum for all our projects: this tool proved to be more effective to manage our projects with team members who may be in the movement or the client. It takes a little more time to write stories and tasks at startup, but this time it is offset by the automatic comfort of graphics burn up and burned down!

Be rigorous demand Scrum Master, but once took the taste of the MELES, difficult to do without! I'm amazed me for the famous table all A4 sheets doing / DONE ' and paste pieces of sticky for a project where I'm only in it!

«journals» actually allows continue the development of an application and above all, above all: don't forget tasks which trainent! a design element that lacks a text to change. See together the tasks you do every day and monitor the evolution curve allows you to stay focused, do not release the effort until the final delivery.

BurnDown

At the end of the sprint, the retrospective allows you to take the recoil and improve our performance as a team. Analysis of quack Pack organization and solutions is in the next sprint. More makes this point seriously, working better together! There is nothing that this is top!

I confess to be sceptical about the SCRUM at the beginning, I admit it now be convinced!

Cut function allows us to perform application blocks, forces us to design the application architecture as the developments. This is complicated when you start on a platform, but it becomes simple about the experience.

Phoneblocks, un téléphone scrum ? ;)

However, the free choice of technologies for the development of the application, more involves us in the project. Also, the fact that each one of the developers on the team allocated tasks that want to get energized by the progress of the project and motivates us.

The various meetings make the most effective developments.

In fact, sprint meetings start allows us to be aware of the features to develop by the end of the sprint and cut in simple tasks. "diaries" will allow us to review progress by each the day before to see the progress of tasks and identifypain points so that equipment can be adapted to the abilities of each.

In the same way, at the end of the sprint meetings allow us make a point about the progress of the development of the characteristics of the project and give our feelings to suit the workload or the review of methods of work for the next Sprint. This meeting is an opportunity to have a preview of the application that we develop and even more in its realization motivates us.

I find many advantages to using Scrum methodology in my test phases. Firstly, with the "diaries", I am more involved in design and features allows you to create new angles of attack to identify possible errors. On the other hand, my scenarios and test cases evolve throughout the sprints. With this daily monitoring, I know when completed all tasks of development, so I can adjust my winning time and schedule flexibility.

Be incorporated in the sprints, the phases of evidence are also more reactive. And each property be well cloisonee, edge effects are more limited, therefore limiting the amount of evidence.

Tests have finally the importance should be all the time : a history is not declared over until there are no mistakes in it!

chuck

vendredi 8 novembre 2013

Le Scrum, deux ans après

scrum1

Voilà bientôt deux ans que Haploid a choisi la méthodologie SCRUM pour l’ensemble de ses projets.

Voici un petit retour d’expérience vu par chacun des rôles clés du SCRUM : Développeur, Testeur, Scrum Master et Product Owner

Mon rôle de Product Owner se résume à comprendre le besoin du client, l’objectif est de refléter au maximum ses attentes et surtout ses ambitions ! Je reçois régulièrement des cahiers des charges de plusieurs dizaines de pages pour une application mobile, après avoir lu les 20 premières pages, vous avez déjà oublié la première fonctionnalité.

Un cahier des charges ne permet pas non plus de pondérer chaque fonctionnalité en fonction de son apport « business », autrement dit quelle fonctionnalité va générer le plus de revenus dans mon application ?

La méthode SCRUM permet d’éclater ce cahier des charges en « user stories » qui permettent d’évaluer la complexité de réalisation et la « business value ». Cette étape est un excellent moyen pour faire comprendre à notre client que toutes les fonctionnalités ne se valent pas et qu’il est capital que les plus « importantes » soient développées en amont.

L’autre avantage du SCRUM est la livraison fréquente du produit, à chaque fin de sprint, notre client est en mesure de tester et valider les « user stories » implémentées. On évite ainsi les mauvaises surprises liées au « tunnel de développement ».

Ces interactions fréquentes apportent de la confiance et permettent de travailler en concertation tout au long du projet. Tous les clients qui ont su s’adapter à cette méthodologie (disponibilité lors des réunions de fin sprint, participations aux daily) ont apprécié cette transparence vis à vis des équipes.

logo

Pour tous nos projets nous utilisons IceScrum : Cet outil s’est révélé le plus efficace pour gérer nos projets avec des membres de l’équipe qui peuvent être en déplacement ou avec le client. Il faut un peu plus de temps pour écrire les stories et les tâches au démarrage mais ce temps est compensé par le confort des graphiques de burn-up et burn-down automatiques !

Être Scrum Master demande de la rigueur, mais une fois qu’on a pris goût au SCRUM, difficile de s’en passer ! Je me surprend même a faire sur des feuilles A4 le fameux tableau « TODO / DOING / DONE » et à y coller des bouts de post-it pour un projet où je suis tout seul dessus !

Les « dailys » permettent de vraiment bien suivre le développement d’une application et surtout, surtout : de ne pas oublier de tâche qui trainent ! un élement de design qui manque, un texte à changer. Voir ensemble les tâches à faire tout les jours et surveiller la courbe du burndown permet de rester concentré, de ne pas relâcher l’effort jusqu’à la livraison finale.

BurnDown

En fin de sprint, la rétrospective permet de prendre du recul et améliorer notre fonctionnement en tant qu’équipe. On analyse les couacs d’organisation et on essaye des solutions au sprint suivant. Plus on fait ce point sérieusement, mieux on travaille ensemble ! rien que ça c’est top !

J’avoue avoir été sceptique sur le SCRUM au début, j’avoue maintenant être fermement convaincu !

Le découpage en fonctionnalités nous permet de réaliser des blocs de l’application, nous obligeant à concevoir l’architecture de l’application au fur et à mesure des développements. Ceci est compliqué lorsqu’on débute sur une plate-forme, mais devient plus simple au fil de l’expérience.

Phoneblocks, un téléphone scrum ? ;)

Cependant, le libre choix des technologies utilisées pour le développement de l’application, nous implique d’autant plus dans le projet. De même, le fait que chacun des développeurs de l’équipe s’attribue lui-même les tâches qu’il souhaite réaliser dynamise l’avancement du projet et nous motive.

Les différentes réunions rendent les développements plus efficaces.

En effet, les réunions de début de sprint nous permettent de prendre connaissance des fonctionnalités à développer pour la fin du sprint et de les découper en tâches simples. Les “dailys” nous permettent de revenir sur les développements réalisés par chacun la veille afin de constater l’avancement des tâches et d’identifier les points de blocage afin que l’équipe puisse s’adapter aux compétences de chacun.

De même, les réunions de fin de sprint nous permettent de faire un point sur l’avancée du développement des fonctionnalités du projet et de donner notre ressenti afin d’adapter la charge de travail ou revoir les méthodes de travail pour les prochains sprints. Cette réunion est l’occasion également d’avoir un aperçu de l’application que nous développons et nous motive d’autant plus dans sa réalisation.

Je trouve beaucoup d’avantages à utiliser la méthodologie Scrum dans mes phases de test. D’une part, avec les « dailys », je me sens plus impliqué dans la conception des fonctionnalités et cela me permet de créer de nouveaux angles d’attaques pour déceler les éventuels bugs. D’autre part, mes scénarios et cas de test évoluent tout au long des sprints. Avec ce suivi journalier, je sais quand toutes les tâches de développement sont terminées, je peux donc ajuster mon emploi du temps gagnant ainsi en flexibilité.

Etant intégrées aux sprints, les phases de tests sont aussi plus réactives. Et chaque fonctionnalité étant bien cloisonée, les effets de bord sont plus restreints, limitant ainsi la quantité de tests.

Les tests ont enfin l’importance qu’ils devraient avoir tout le temps : une story n’est pas déclarée finie tant qu’il reste des bugs la concernant !

chuck

dimanche 20 octobre 2013

Two years later, the Scrum

 


They are almost two years that haploids chose the SCRUM methodology for all your projects.


Here is a small feedback seen by each of the key functions of the SCRUM: developer, Tester and Scrum Master, product owner


My role as owner of the product is reduced to understand the customer's need, the goal is to reflect the highest expectations and above all its ambitions. Regularly receive the specifications of several tens of pages for a mobile application, after having read the first 20 pages, it has already forgotten the first feature.


A specification does not weigh each characteristic according to their contribution 'business', i.e. do functionality generate revenue more in my application?


The method SCRUM to exploit this specification in "user stories" to assess the complexity of the preparation and the value for the business. This step is an excellent way to understand our customer that all functions are not worth and is crucial to the more 'important' to be developed against the current.


The other advantage of the SCRUM is the frequent delivery of the product, at each end of the sprint, our client is able to test and validate the implemented "user stories". This prevents unpleasant surprises related to the "development tunnel.


These frequent interactions bring confidence and work together throughout the project. All customers who were able to adapt this methodology (the availability of meetings well sprint, participation in the newspaper) enjoyed this equipment vis-à-vis transparency.


logo


Use IceScrum for all our projects: this tool proved to be more effective to manage our projects with team members who may be in the movement or the client. It takes a little more time to write stories and tasks at startup, but this time it is offset by the automatic comfort of graphics burn up and burned down!


Be rigorous demand Scrum Master, but once took the taste of the MELES, difficult to do without! I'm amazed me for the famous table all A4 sheets doing / DONE ' and paste pieces of sticky for a project where I'm only in it!


«journals» actually allows continue the development of an application and above all, above all: don't forget tasks which trainent! a design element that lacks a text to change. See together the tasks you do every day and monitor the evolution curve allows you to stay focused, do not release the effort until the final delivery.


BurnDown


At the end of the sprint, the retrospective allows you to take the recoil and improve our performance as a team. Analysis of quack Pack organization and solutions is in the next sprint. More makes this point seriously, working better together! There is nothing that this is top!


I confess to be sceptical about the SCRUM at the beginning, I admit it now be convinced!


Cut function allows us to perform application blocks, forces us to design the application architecture as the developments. This is complicated when you start on a platform, but it becomes simple about the experience.


 


However, the free choice of technologies for the development of the application, more involves us in the project. Also, the fact that each one of the developers on the team allocated tasks that want to get energized by the progress of the project and motivates us.


The various meetings make the most effective developments.


In fact, sprint meetings start allows us to be aware of the features to develop by the end of the sprint and cut in simple tasks. "diaries" will allow us to review progress by each the day before to see the progress of tasks and identifypain points so that equipment can be adapted to the abilities of each.


In the same way, at the end of the sprint meetings allow us make a point about the progress of the development of the characteristics of the project and give our feelings to suit the workload or the review of methods of work for the next Sprint. This meeting is an opportunity to have a preview of the application that we develop and even more in its realization motivates us.


I find many advantages to using Scrum methodology in my test phases. Firstly, with the "diaries", I am more involved in design and features allows you to create new angles of attack to identify possible errors. On the other hand, my scenarios and test cases evolve throughout the sprints. With this daily monitoring, I know when completed all tasks of development, so I can adjust my winning time and schedule flexibility.


Be incorporated in the sprints, the phases of evidence are also more reactive. And each property be well cloisonee, edge effects are more limited, therefore limiting the amount of evidence.


Tests have finally the importance should be all the time : a history is not declared over until there are no mistakes in it!


 

vendredi 18 octobre 2013

Two years later, the Scrum

 


They are almost two years that haploids chose the SCRUM methodology for all your projects.


Here is a small feedback seen by each of the key functions of the SCRUM: developer, Tester and Scrum Master, product owner


My role as owner of the product is reduced to understand the customer's need, the goal is to reflect the highest expectations and above all its ambitions. Regularly receive the specifications of several tens of pages for a mobile application, after having read the first 20 pages, it has already forgotten the first feature.


A specification does not weigh each characteristic according to their contribution 'business', i.e. do functionality generate revenue more in my application?


The method SCRUM to exploit this specification in "user stories" to assess the complexity of the preparation and the value for the business. This step is an excellent way to understand our customer that all functions are not worth and is crucial to the more 'important' to be developed against the current.


The other advantage of the SCRUM is the frequent delivery of the product, at each end of the sprint, our client is able to test and validate the implemented "user stories". This prevents unpleasant surprises related to the "development tunnel.


These frequent interactions bring confidence and work together throughout the project. All customers who were able to adapt this methodology (the availability of meetings well sprint, participation in the newspaper) enjoyed this equipment vis-à-vis transparency.


logo


Use IceScrum for all our projects: this tool proved to be more effective to manage our projects with team members who may be in the movement or the client. It takes a little more time to write stories and tasks at startup, but this time it is offset by the automatic comfort of graphics burn up and burned down!


Be rigorous demand Scrum Master, but once took the taste of the MELES, difficult to do without! I'm amazed me for the famous table all A4 sheets doing / DONE ' and paste pieces of sticky for a project where I'm only in it!


«journals» actually allows continue the development of an application and above all, above all: don't forget tasks which trainent! a design element that lacks a text to change. See together the tasks you do every day and monitor the evolution curve allows you to stay focused, do not release the effort until the final delivery.


BurnDown


At the end of the sprint, the retrospective allows you to take the recoil and improve our performance as a team. Analysis of quack Pack organization and solutions is in the next sprint. More makes this point seriously, working better together! There is nothing that this is top!


I confess to be sceptical about the SCRUM at the beginning, I admit it now be convinced!


Cut function allows us to perform application blocks, forces us to design the application architecture as the developments. This is complicated when you start on a platform, but it becomes simple about the experience.


Phoneblocks, un téléphone scrum ? ;)


However, the free choice of technologies for the development of the application, more involves us in the project. Also, the fact that each one of the developers on the team allocated tasks that want to get energized by the progress of the project and motivates us.


The various meetings make the most effective developments.


In fact, sprint meetings start allows us to be aware of the features to develop by the end of the sprint and cut in simple tasks. "diaries" will allow us to review progress by each the day before to see the progress of tasks and identifypain points so that equipment can be adapted to the abilities of each.


In the same way, at the end of the sprint meetings allow us make a point about the progress of the development of the characteristics of the project and give our feelings to suit the workload or the review of methods of work for the next Sprint. This meeting is an opportunity to have a preview of the application that we develop and even more in its realization motivates us.


I find many advantages to using Scrum methodology in my test phases. Firstly, with the "diaries", I am more involved in design and features allows you to create new angles of attack to identify possible errors. On the other hand, my scenarios and test cases evolve throughout the sprints. With this daily monitoring, I know when completed all tasks of development, so I can adjust my winning time and schedule flexibility.


Be incorporated in the sprints, the phases of evidence are also more reactive. And each property be well cloisonee, edge effects are more limited, therefore limiting the amount of evidence.


Tests have finally the importance should be all the time : a history is not declared over until there are no mistakes in it!


 

mercredi 9 octobre 2013

Two years later, the Scrum

 


They are almost two years that haploids chose the SCRUM methodology for all your projects.


Here is a small feedback seen by each of the key functions of the SCRUM: developer, Tester and Scrum Master, product owner


My role as owner of the product is reduced to understand the customer's need, the goal is to reflect the highest expectations and above all its ambitions. Regularly receive the specifications of several tens of pages for a mobile application, after having read the first 20 pages, it has already forgotten the first feature.


A specification does not weigh each characteristic according to their contribution 'business', i.e. do functionality generate revenue more in my application?


The method SCRUM to exploit this specification in "user stories" to assess the complexity of the preparation and the value for the business. This step is an excellent way to understand our customer that all functions are not worth and is crucial to the more 'important' to be developed against the current.


The other advantage of the SCRUM is the frequent delivery of the product, at each end of the sprint, our client is able to test and validate the implemented "user stories". This prevents unpleasant surprises related to the "development tunnel.


These frequent interactions bring confidence and work together throughout the project. All customers who were able to adapt this methodology (the availability of meetings well sprint, participation in the newspaper) enjoyed this equipment vis-à-vis transparency.


 


Use IceScrum for all our projects: this tool proved to be more effective to manage our projects with team members who may be in the movement or the client. It takes a little more time to write stories and tasks at startup, but this time it is offset by the automatic comfort of graphics burn up and burned down!


Be rigorous demand Scrum Master, but once took the taste of the MELES, difficult to do without! I'm amazed me for the famous table all A4 sheets doing / DONE ' and paste pieces of sticky for a project where I'm only in it!


«journals» actually allows continue the development of an application and above all, above all: don't forget tasks which trainent! a design element that lacks a text to change. See together the tasks you do every day and monitor the evolution curve allows you to stay focused, do not release the effort until the final delivery.


BurnDown


At the end of the sprint, the retrospective allows you to take the recoil and improve our performance as a team. Analysis of quack Pack organization and solutions is in the next sprint. More makes this point seriously, working better together! There is nothing that this is top!


I confess to be sceptical about the SCRUM at the beginning, I admit it now be convinced!


Cut function allows us to perform application blocks, forces us to design the application architecture as the developments. This is complicated when you start on a platform, but it becomes simple about the experience.


 


However, the free choice of technologies for the development of the application, more involves us in the project. Also, the fact that each one of the developers on the team allocated tasks that want to get energized by the progress of the project and motivates us.


The various meetings make the most effective developments.


In fact, sprint meetings start allows us to be aware of the features to develop by the end of the sprint and cut in simple tasks. "diaries" will allow us to review progress by each the day before to see the progress of tasks and identifypain points so that equipment can be adapted to the abilities of each.


In the same way, at the end of the sprint meetings allow us make a point about the progress of the development of the characteristics of the project and give our feelings to suit the workload or the review of methods of work for the next Sprint. This meeting is an opportunity to have a preview of the application that we develop and even more in its realization motivates us.


I find many advantages to using Scrum methodology in my test phases. Firstly, with the "diaries", I am more involved in design and features allows you to create new angles of attack to identify possible errors. On the other hand, my scenarios and test cases evolve throughout the sprints. With this daily monitoring, I know when completed all tasks of development, so I can adjust my winning time and schedule flexibility.


Be incorporated in the sprints, the phases of evidence are also more reactive. And each property be well cloisonee, edge effects are more limited, therefore limiting the amount of evidence.


Tests have finally the importance should be all the time : a history is not declared over until there are no mistakes in it!