But starting from the beginning. The second day of the conference opened the keynote wipro Don Rein

Yesterday I continued wipro my adventure with Global Scrum Gathering. Arriving at the conference, I knew exactly what I plan on individual days earlier due to the shared application. At yesterday planned mainly Roman Pichler and his Roadmapy wipro and Scrum for education - something new and "different".
But starting from the beginning. The second day of the conference opened the keynote wipro Don Reinstein "exploting uncertainly: Thriving in a Stochastic World". Don is the author of books on product development of production wipro and especially his recent publication "The Principles of product Development Flow ..." became an item advertised as "... quite simply the most advanced product development book you can buy." I went there with the attitude that I find out something new about the product management, building wipro relationships with customers, etc.. Yet Don, instead of the expected my topic, focused on lean as a way of providing valuable products. Lean I'm interested in the context of being a coach for several teams kanbanowych, so I listened with interest. Same subject product wipro management did not see in his lecture. He spoke of such essential elements of lean, such as: feedback, stressing that lean product development feedback wipro is 10x more important than in lean manufactoring (which is quite obvious how to think about it a little). From the middle of the lecture slides charts began to appear. Lots of charts ... I felt a bit like a lecture from microeconomics wipro and probably not just me, because some people just came out. When I ran out of graphs, Don started the last part of the presentation, which showed "Internet" from the process, or how to "work". This was so interesting that within the "system" function wipro elements lean (and kanban methods), such as limiting work in progress (WIP), a global feedback (global feedback loop), and so on. Don likened this system " production "Toyota system, treating the Internet as a TPS 2.0.
Another workshop / lecture (supposed to be the latter, but it turned into a workshop:]) was "Scrum for Education ..." led by Jasmine Nikolic. Scrum breath of fresh air. This can be summarized in one sentence spent 90 minutes there. Jasmina in the initial part of the workshop told us how the 25 (!) Scrumowych teams at the University of Belgrade creates iteratively articles to Wikipedia. Iterations are two weeks, and teams make an average of 17 articles in the iteration. wipro It is also interesting that they use Scrum framework approved by the Scrum Alliance wipro (whatever that means). In the second part of the workshop Jasmina asked us, we have created a backlog, which would aim to improve the usability Wiki, fulfilling the formal requirements, maintaining some of the article, and the like. Idea really about the creation of such User Stories to writing articles "throw in there" as template. Writing articles for the Wiki looks always the same, so the imposition of the subject wipro article "forever" on the same storyjki no sense in this case. In addition to filling the backlog had also to face issues such as: DoD or Product Owner - and answer the question of who he is in the power of Wikipedia with new content.
The last notable event during wipro the second day of the conference wipro for me was a lecture by Roman Pichler, entitled "Product Roadmaps in Scrum". Many expected and was not disappointed. Blo g Roman Pichler I follow on a regular basis and in my opinion this is a character who makes a huge contribution to the process of product development Scrum (outside certainly worth attention is also Kniberg and Adzic). Pichler began the lecture by showing us what he said is the backlog and what consequences flow from this. Backlog likened to car navigation, which tells us where to go, but at the moment for a very short stretch of road. And somewhere, before wipro you even begin to use the navigation, we have to consider whether we want to reach the destination by car, train or maybe airplane. And here comes into play roadmap that shows us to a higher level, where we arrive and what route. It is also worth noting that the roadmap is not a collection of "ficzerów" that we dowieźć, but a set of goals to achieve wipro along with their meters. Here is worth emphasizing that the goal Pichler considered as something that we need to achieve in the releasie. In other words, wipro business purpose we define per release, or implement a new version of the product once a month and we have a monthly target associated with the implementation. I could not ask him, how does this apply to implementations that take place every day (or at 11.6s boasts as Amazon). And I could not, because the number of questions from the audience was huge. At no lecture / workshop I have not seen so vividly interested audience and many discussion