Doorgaan naar hoofdcontent

Dream Event 2013

On Thursday the 12th of september I visited the Dream Event in Houten. This is a small recap of the event.

Theme

Dream stands for Dutch Requirement Engineering And Management and is the only event within the Netherlands specifically about Requirements. The event had some very interesting speakers, of which James Taylor is probably the most famous one. The presentations were very diverse and with some kind of relation towards requirements of course.

James Taylor - Simpler, smarter and more agile processes

His talk was about making processes simpler, smarter and more agile by using business rules. So looking at if-the-else constructions within the processes, that have high impact on the processes. Not the best presentation i have seen, but this is my personal opinion. It was very formal and not much new information for me. It should be common practive when you want to have your processes flexible and agile. I do understand though that this is probably not common sense in most organisations.

Rini van Solingen - Survival of the fittest, bringing business value quick

This was a very entertaining and interested presentation of Rini. The presenation was done without the usual powerpoints, but he draw things on a flipover. He stated (among other things) that planning does not work anymore in this fast society. In the past he argued that there was time to grow. He used the example that it took the telephone 75 years to reach 50 million users. Nowadays Angry Birds reached this figure within 13 days. The statement is clear because organisations are organized as fabrics of the 19th century. And this does not work (at least not for a lot of produkts) any more. He states that Agility is key with timeboxing, steady teams and steady quality.
I think he has some good points, but steady teams and steady quality can be difficult to achieve.

Some other statements he made:
  • You learn more by doing things than by thinking about it
    I agree on this when it comes to software development and this is also why Agile development is such a "hype" at the moment. We are not able to specify each requirement in such detail, so that it does not change anymore. You have to see it working.
  • The organisation F-Secure uses the following KPIs
    - Lead time must go down
    - Value throughput must raise
    - Net promotion score mus raise
    - Number of unfinished work must go down
    So faster time to market, with higher business value and high customer satisfaction, but the work must be finished.
Some conclusions he made:
  • Make cross functional teams
  • Fast csutomer value
  • Focus on results and transparency
  • Realy change the game
  • Making mistakes is a MUST

Arjen  Uittenbogaard - 7 essential characteristics of an agile professional

The most interesting and inspiring presentation came from Arjen. He is a real storyteller with a great sense of humor and great presentation skills. He also used no powerpoints and also no flipover. He talked about three books:
  1. Intensieve menshouderij - Jaap Peters (Dutch)
    Within this book it is argued that "measuring is not always knowing". Numbers is narrowing your view. SMART is not always smart.
    Be aware of the language of the customer and do not "frame". Discover the metaphors used.
  2. Practical Wisdom - Barry Swartz
    The short message is: Does making Rules and following rigid processes really improve the work?
    The statement of the book is that it is disastrous for craftsmanship. The examples in the book are mainly on healthcare and law, but i agree that rules must not be followed blindly but always used within the context and as a tool.
  3. To save everything click here
    This is a more philosophical book about the question if innovations are really the solution to a problem. 
I bought all three books and i am very excited about them. Real eye-openers !

Conclusion

A real nice organised conference with a lot of interesting speakers. Happy i could attend.

Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin