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.
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!
Aucun commentaire:
Enregistrer un commentaire