[#ALM] Agile Customers are a #MustHave (and of course this to use Microsoft Feedback Client)

Hello!

Yesterday I make a statement: if we want to have visible results, the first distinction that we have to do; is not to be oriented in the technology trend (or architecture or development roles) but instead try to create a context orientated to the business itself; in this team work you’ll fin customers and the agile team. And of course, very a important part of it are clients or customers.

Caution! we should not confuse these roles with the Product Owner we know of SCRUM. According to the Guide, PO is the main author of the User Stories, he manages the Product Backlog, he defines the priority of the stories, he defines the acceptance tests, and he approves the work carried out by the Agile Team. However, that is not a “real customer”; a true customer is involved in an early stage and he is the one who detects a problem or a need and which will use the final solution created by the team. In an Agile Team it is very important to involve a person with the knowledge of business from day one, but the question always remains: Is this person a real reflection of a client?

Note:My short experience has taught me that when more time working with these experts from business, more we begin to know the business and can improve our solution. The tradeoff is that these SMEs also begin to learn how an Agile Team and are adapting to the team practices. This is not bad, however it can be counter-productive if not is valid with the other “clients”.

My answer to this is: The solution to meet an end customer, does not go through involving all clients within the development team, but instead think to plan some type of activity to obtain feedback from them. The concept of Agile Customer implies that we work partially with an on-site Customer (that in the long run you end up making the Product Owner and if you have good luck this work is not in part but full time). As an addition to this concept I would like to add the following activities

  • In a Sprint Review, integrate not only the familiar faces of the project; It tries to involve new people. At a previous session or at the beginning of the meeting, you spend time to explain the purpose of the Sprint Review and the dynamics of work; and he tries to get his feedback during the same.
  • Remember the 2 fundamental premises related to dealing with customers
  • Do not implement anything that has not been approved by a client
  • Nobody can replace an end user of the application
  • Use tools such as “Request Feedback” from Team Foundation Server or Visual Studio Online to engage these people and have a frequent Feedback on the progress of the application.

    image

    Finally, remember that while change is a constant, a closed version depends on the capacity that we have to manage the expectations of our customers. Be honest and be solution a success.

    References: If you want to know more about Microsoft Feedback Client you can see my posts here.

  • Saludos @ La Finca

    El Bruno

    image image image Google
    Advertisements

    [#ALM] Welcome to Agile Customers (y porque no, Microsoft Feedback Client)

    Hola!

    Ayer quedó claro que, si queremos tener resultados visibles, la primera distinción que debemos realizar no tiene que estar orientada hacia la tecnología (o arquitectura o roles de desarrollo) sino al contexto donde se creará la solucion; este contexto está formado por customers y por el equipo de trabajo. Una parte muy importante de la misma son los clientes o customers.

    Ojo, no debemos confundir a estos roles con el Product Owner que conocemos de SCRUM. Según la guía el PO es el principal autor de las User Stories, maneja el Product Backlog, define la prioridad de las historias, define los tests de aceptación y aprueba el trabajo realizado por el Agile Team. Sin embargo, ese no es el “cliente”; el verdadero cliente es el que en un estadio inicial detecta un problema o necesidad y es el que utilizará la solución final creada por el equipo. En un Agile Team es muy importante involucrar a una persona con los conocimientos de negocio desde el día cero, pero siempre queda la pregunta: ¿es esta persona un real reflejo de un cliente?

    Nota: Mi corta experiencia me ha enseñado que cuando más tiempo trabajamos con estos expertos de negocio, más comenzamos a conocer el negocio y podemos mejorar nuestra solución. La contrapartida es que estos SMEs también comienzan a conocer como funciona un Agile Team y se van adaptando a las prácticas del equipo. Esto no es malo, sin embargo puede resultar contraproducente si no se valida con los demas “clientes”.

    La solución para conocer a un cliente final, no pasa por involucrar a todos los clientes dentro del equipo de desarrollo, pero si planificar algún tipo de actividad para obtener feedback de los mismos. El concepto de Agile Customer implica que trabajemos de forma parcial con un On-Site Customer (que a la larga se termina convirtiendo en el Product Owner y si tienes mucha suerte este trabajo no es en forma parcial sino full time). Como un adicional a este concepto me gustaría agregar las siguientes actividades

    • En una Sprint Review, no solo incorpores las caras conocidas del proyecto; intenta involucrar a nuevas personas. En una reunión previa o al principio de la reunión, dedica un tiempo para explicarle el objetivo del Sprint Review y la dinámica de trabajo; e intenta obtener su feedback durante el mismo.
    • Recuerda las 2 premisas fundamentales relacionadas con el trato con los clientes
    • NO IMPLEMENTES NADA que no haya sido aprobado por un cliente
    • NADIE puede sustituir a un usuario final de la aplicación
  • Utiliza herramientas como “Request Feedback” de Team Foundation Server o Visual Studio Online para involucrar a estas personas y tener un Feedback frecuente sobre el avance de la aplicación.
  • image

    Para finalizar recuerda que si bien el cambio es una constante, una versión cerrada depende mucho de la capacidad que tengamos de manejar las expectativas de nuestros clientes. Se honesto y la solución seá un éxito.

    Referencias: Si quieres saber más sobre Microsoft Feedback Client puedes ver mis posts aquí.

    Saludos @ La FInca

    El Bruno

    image image image Google

    [#ALM] Do you really need roles in a team? (usually not)

    Hello!

    Today I’m going to avoid the intro and some context and I’ll go directly to the question:

    Are necessary roles in an Agile team ?

    The answer is simple: Yes. But they are not roles that usually people know, there are only 2 roles in a single Agile Team

    • Some people with a problem
    • An Agile Team with the ability to provide a solution to this problem

    And that’s all. The 1st role is usually known as a client or customer, and is defining the problems or needs that will work the 2nd team. The 2nd team is where lives the usual roles, best-known as front end developer, backend roles developer, analyst, etc.

    The important thing in an agile team is that members should be flexible enough to cover any position. Since the ZERO day, the team should be able to to add value. This does not remove the need for some specialist, in example: a tuning of a databases. This should be be dictated by the evolution of the solution, and if the architecture is emerging from the team, there will not be a problem. (remember discarded classical architects! ))

    And I’ll close with a tip: The next time that you start an agile team, don’t consider the specific capacities of the people in relation to what they can do, but rather keep in mind the capacity that they have to adapt to what comes up. Remember that the only constant in a team change and:

    Agile customers knows that a product can always improve, and also knows that they are responsible for the changes introduced in the product

    Analysts knows that a solution is never complete, the context and the problems tend to change and they must adapt the analysis models as these changes are discovered

    The developers know that we will never write perfect code, so that we refactor the code, we base our code on tests and change the code again and again to improve it

    Happy Teaming Open-mouthed smile !!!

    Saludos @ Home

    El Bruno

    image image image Google

    [#AVANADE] Avanade teams up with Scrum.org !!!

    Hola!

    Por dios … el viernes en el #CommunityDay14 me estuve comiendo las uñas al lado de grandes como Luis Fraile, Rodrigo Corral, Vicent Alves, JC y otros para no comentar la noticia.

    Ahora sí, después de varios años de trabajo en conjunto con Scrum.org, hemos llegado a un acuerdo para poder tener un Agility Path dentro de Avanade. Esto tiene muchos matices, sin embargo lo que personalmente puedo resaltar es que trabajar con la gente de Scrum.org no es fácil, es un placer pero no es fácil. Este acuerdo toca a Avanade desde adentro, en temas como colaboración, training, certificaciones, etc. Hacer esto en una empresa de 20000 empleados, les aseguro que no es una tarea fácil.

    Pero el resultado hoy es 100% GRATIFICANTE !!! después de muchos años de conversaciones (los que conocen las grandes corporaciones sabrán apreciar esto más que nadie)

    Saludos @ Home

    El Bruno

    image image image Google

    [#ALM] #Waterfall process are not legal for the DoD

    Hello!

    Finally someone eventually realizing that it is meaningless to continue working using Waterfall models. And, if the Ministry of Defense of the United States declares it so, you should listen isn’t it?

    If you ask me to me, in fact illegal should not be the waterfall model, but rather the “no conversion to an Agile model”. It seems that I would like everyone to be part of a cult, and there is something of that. However, is a model who in addition to being guided by well-defined principles, as well… results (which are not always good, but they are results!).

    Source: http://nakedalm.com/dod-has-made-it-illegal-to-do-waterfall/?utm_source=buffer & utm_campaign = Buffer & utm_content = buffer2d113 & utm_medium = facebook

    Greetings @ Home

    The Bruno

    imageimageimageGoogle

    [#ALM] Y el día llego: #Waterfall es ILEGAL para el DoD

    Hola!

    al final alguien se terminaría dando cuenta de que es un sinsentido seguir trabajando con modelos Waterfall. Y, si el Ministerio de Defensa de los Estados Unidos lo declara así, por algo será, ¿no?

    Si me preguntan a mi, en realidad lo ilegal no debería ser el modelo waterfall, sino más bien la “no conversión a un modelo Agile”. Parece que quisiera que todo el mundo sea parte de una secta, y algo de eso hay. Sin embargo, es un modelo que además de estar guiado por unos principios bien definidos, pues bien .. da resultados (que no siempre son buenos, pero son resultados!).

    Fuente: http://nakedalm.com/dod-has-made-it-illegal-to-do-waterfall/?utm_source=buffer&utm_campaign=Buffer&utm_content=buffer2d113&utm_medium=facebook

    Saludos @ Home

    El Bruno

    imageimageimageGoogle

    [#EVENT] Materials of the event of working AGILE with #VS2012 and #TFS2012

    image

    Good

    after passing incredible 60 minutes with MSDN Latam people talking about how it is possible to work with Visual Studio 2012 and Team Foundation Server 2012, my turn comply with promised: share the presentation, some links, etc.

    Definition of DONE

    http://blogs.msdn.com/b/willy-peter_schaub/archive/2013/03/21/definition-of-done-and-knowing-when-it-is-safe-to-sleep-peacefully.aspx
    Something essential that must be clear from day one.

    Books

    TFS WebCast Express

    https://elbruno.com/2013/03/11/event-msdn-latam-webcast-msdn-todos-a-bordo-del-team-foundation-server-express/
    https://msevents.microsoft.com/CUI/EventDetail.aspx?culture=es-AR & EventID = 1032547149 & CountryCode = AR

    Planning Poker Online

    http://www.planningpoker.com/
    It is free and they can work in a distributed without any problem.

    And finally the presentation

    Saludos @ La Finca

    El Bruno

    image image image

    [#EVENT] Materiales del evento de trabajo AGILE con #VS2012 y #TFS2012

    image

    Buenas

    después de pasar unos 60 minutos increíbles con la gente de MSDN Latam hablando sobre cómo es posible trabajar con Visual Studio 2012 y Team Foundation Server 2012, me toca cumplir con lo prometido: compartir la presentación, algunos links, etc.

    Definition of DONE


    http://blogs.msdn.com/b/willy-peter_schaub/archive/2013/03/21/definition-of-done-and-knowing-when-it-is-safe-to-sleep-peacefully.aspx
    Algo imprescindible que tiene que estar claro desde el día uno.

    Libros

    WebCast TFS Express


    https://elbruno.com/2013/03/11/event-msdn-latam-webcast-msdn-todos-a-bordo-del-team-foundation-server-express/
    https://msevents.microsoft.com/CUI/EventDetail.aspx?culture=es-AR&EventID=1032547149&CountryCode=AR

    Planning Poker Online


    http://www.planningpoker.com/
    Es gratis y pueden trabajar de forma distribuida sin ningun problema.

    Y finalmente la presentación

     

    Saludos @ Home

    El Bruno

    image image image