AgileByExample 2016

AgileByExample 2016

Rafał Markowicz

Code Sprinters

Rafał is a Scrum Master with several years of experience, he participates in various IT projects since 2001. He is an Agile practitioner working with (and often within) development teams, helping them as an expert in test engineering and quality assurance. He used to work as a system and business analyst, he is an experienced developer, manager and consultant.
Rafał worked with telecommunication systems, computerized reservation systems, investment banking, web technologies and mobile applications. He remains an active developer specialized in agile testing and improvements of software development processes. He uses tools and practices like CI, BDD, ATDD, Specification by Example, he also participates in requirements gathering and helps Product Owners to form product backlogs. Rafał often acts as a consultant or hand-son leader of the teams he works with.
As Scrum Master, Rafał focuses on team forming, helping them to become mature and productive. He holds “Professional Scrum Master I” and “Scaled Professional Scrum” certificates issued by He helped organizations to adopt Agile (Scrum or Kanban System) and migrate from traditional approach to agile methods. During trainings he refers to his experiences from work within development teams to show how Agile, empiricism and servant leadership can influence quality and value of crafted software.
Rafał conducts trainings covering Agile, Scrum and Kanban, he also shares his knowledge about testing and quality assurance. He teaches how to formulate requirements (for instance in form of user stories), how to decompose epic requirements into smaller chunks of functionality, how to define acceptance criteria, how to work with non-functional requirements (and, in particular, how to assure performance of complex systems).

Rafał will run his workshop with Andy Brandt.

Workshop—Story Mapping

Story Mapping is a technique that allows better understanding of your product requirements than traditional product backlogs, with key functional areas as one dimension and importance/urgency/value being second dimension. Such a map provides “the big picture” and enables strategic thinking about the product and its development. It also makes it easier to understand and satisfy contrary demands and priorities of different stakeholders of complex solutions. The last but not the least, story maps visualize journey of users through your product as a whole; knowing this, it is easier to develop solution that your users will love.

At Story Mapping Dojo participants will create a story map for a product. Two trainers will help everybody to dive into the right context by providing short outline of a product and by assigning them roles to play during the exercise (example of roles: stakeholder, product owner, developer, manager). Once the map is ready, it will be used to identify possible Minimal Viable Product and possible release strategies.

After the Dojo participants would understand what Story Maps are and how they can be useful, especially for working with requirements for new products and large systems.