In the Domain Driven Design world everyone points to the ubiquitous language as paramount to the success of the project. However, often the developers fall under the pitfall of the technical jargon; the business assumes the developers have all the necessary business knowledge, given incomplete requirements; combining all these communication problems leads to frustration, missed opportunities and ultimately to project failure.
Given the miscommunications and misunderstandings between the development and the business, several questions arise: how can you learn to communicate and closely cooperate with the business, or even better be part of the same team? Also, how can you help the business to deliver a clear vision?
In this session, João will show you how to engage the development team and the business using DDD tools and techniques, using Behaviour Driven Development as the central piece to bring everyone closer. If you have a similar experience, or you want to emerge into DDD & BDD, the session is for you!
developers can understand
the business too!
https://joaorosa.io | @joaoasrosa
Software Quality Consultant @ Xebia
"MS-DOS installation diskettes" by Daan Berg is licensed under CC BY-SA 2.0
"Eggling growth" by Maria Keays is licensed under CC BY 2.0
"Universidade de Aveiro " by Paulo Corceiro is licensed under CC BY-ND 2.0
"MBP Backlit Keyboard" by rhodesj is licensed under CC BY 2.0
"Animal Mailbox" by Kecko is licensed under CC BY 2.0
"Stack of blue paper" by Arria Belli is licensed under CC BY-SA 2.0
"SAP Meeting Room" by Vladislav Bezrukov is licensed under CC BY 2.0
"Man working at analog computer, 1968 color corrected" by Mike Grauer Jr is licensed under CC BY 2.0
"Ping Pong in Chaoyang Park" by Marshall Segal is licensed under CC BY-NC-ND 2.0
Mmm, too young, too dumb to realize
Hernandez Peter Gene, Lawrence Philip Martin II
“Burning” by Emilio Küffer is licensed under CC BY-SA 2.0
“Explosion” by Chad Horwedel is licensed under CC BY-NC-ND 2.0
Carrots & Sticks are so last Century. Drive says for 21st
century work, we need to upgrade to autonomy, mastery
Daniel H. Pink
“Light & Learning” by Shadow-or-Light is licensed under CC BY-NC-ND 2.0
“Two-way communication” by Jacob Bøtter is licensed under CC BY 2.0
"network cables" by Pascal Charest is licensed under CC BY-NC-ND 2.0
"Spiral Stairs" by Gabriela Fab is licensed under CC BY-ND 2.0
"Ready to kick!" by Antonio Cinotti is licensed under CC BY-NC-ND 2.0
”Splash" by Cloudtail the Snow Leopard is licensed under CC BY-NC-ND 2.0
To communicate effectively, the code must be
based on the same language used to write the
requirements - the same language that the developers
speak with each other and with domain experts.
”Drift" by www.twin-loc.fr is licensed under CC BY 2.0
”Pair programming" by Damien Pollet is licensed under CC BY-SA 2.0
We start mastering the
techniques, and gain our
But with great power comes great responsibility!
Ialready know it!
”The” Important Business Person
”Bins" by Russel McGovern is licensed under CC BY-NC-ND 2.0
ü Do the first step, speak the same
ü Rename the code to use the same
ü Hack the Agile process, Ask “What if?”
Be aware of ”Why?”
ü Measure the “What if’s”
ü Example Mapping as replacement of the
ü Create Bounded Contexts
ü Pair/Mob Programming
ü Wall of Tech Debt
ü Help the decision makers with
ü EventStorming as tool to facilitate the
Rinse and repeat!
Software development is a learning process, working
code is a side effect.