addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupsimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1outlookpersonJoin Group on CardStartprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Value Stream Mapping a tool to help your team to improve productivity

Are you new to Agile Software Development? Are you struggling to figure out what are the worst points of your software development process? Do you have a feeling that something is wrong but you really don't know what is it? Because you are new to Agile Sw development, you know there are still many silos within your teams but you don't know where are they. Don't worry, we have a great tool that will make all your difficulties visible, helping you to quickly improve your sw development process. If you are interested, come and see my presentation “Value Stream Mapping, a tool to find the weak spots in your value stream. During ours presentation, we will explain how to use Value Stream Mapping and how this tool will easily identify silos within teams/departments. It shows the most of the dependencies within teams, helping you to visualize a full software development process that allows you to take the right measures to improve it. Come and see this useful presentation.

Join or login to comment.

  • Cezary F.

    How the flexibility features (excess workload, changes, cancelling) and test driven development are perceived in the presented method?

    February 13, 2014

    • Luis G.

      Hi Cezary, Yesterday we did not have much time to discuss stuff, I was tired and did not play enough attention to your concerns. I have a suggestion for you. I pay you a nice beer and we go for a beer to discuss this further. How about?

      1 · February 13, 2014

  • Cezary F.

    I left the room not convinced. Let me share my doubts.

    February 13, 2014

  • Cezary F.

    Agile SD was invented to address the main problem of the waterfall process: lack of comprehensive knowledge regarding the customer requirements at the beginning. Instead, we introduced iterative, test driven process that at the end leads us towards the system, which brings the highest value for the customer. In Agile SD we follow the customer needs along ppursuit curve instead of straight line to the target. Obviously, the straight line would be faster, but the target point could have been far from the maximal customer satisfaction. The immanent aspect of iterative model is higher workload than waterfall. We assume also flexibility, changing the direction to follow the current understanding of the customer needs. We believe the cancelling the failed projects is better than following the wrong path till the bitter end. Test driven development is main principle.

    February 13, 2014

  • Gro G.

    sadly can't make it as the family is visiting - Looking forward till next time.

    2 · February 6, 2014

22 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy