Skip to content

Details

User Stories are a great way to capture software requirements. However, after using User Stories for a while,some scenarios start challenging our process and making us wonder if User Stories are still a good tool.

If you asked yourself questions like:

• How can I handle dependency between stories?

• How can I write a story to install a router?

• How can I identify when a story is too big and should be split?

• Is this a story, an Epic or a Saga?

Join us in a session to discover what is beyond writing a user story and make your team more productive!

About the presenter: Amir Barylko started his career in 1994 working for IBM as a senior developer while he was finishing his Masters degree in computer science. Since then he worked as team leader and architect for the past 15 years.
Having started with languages like C++ and Java he spent many years coding in C# and training other developers in topics such domain modeling, abstractions, patterns, automation, dependency injection, testing, etc.
Being an incurable geek, always thirsty for knowledge, his passion for technology moved him towards Ruby on Rails (RoR) a few years ago, becoming an advocate of RoR web development.
Looking for new ways of sharing his knowledge and helping others to achieve their goals motivated Amir to become an owner and build a lean management tool called SmartView (http://smartview.io) that was released in 2014.
Amir is a rare combination of high technical skills, experience in a wide range of platforms, exceptional presentation skills and great sense of humor. His presentations are always rich in content and fun to attend.

Members are also interested in