Scrum doesn’t mandate technical practices explicitly. Neither does kanban. Agile is a set of principles and practices, and it’s often hard to choose which one are useful. There’s a reason to that. Scrum is not a process but a framework that you adapt to your context. Kanban is about introducing change, and it’s up to […]
Agile Challenge: Adopting Technical Practices Read More »
Once upon a time a wish was born in our trainer’s soul: to gather programmers in a place, in Romania where anyone can come, code and go wherever they please. His wide experience and knowledge about programming was built on his own years of programming but also on others experience shared when he met them.
Code&Beer Anniversary Read More »
User Stories are the bridge between the customer and the development team. They are short, clear, written sentences which tell everyone what the system needs to do for the user. For the Agile practitioners, the user stories are known as one of the primary development artifacts for Scrum project teams. Those artifacts resume clearly the requirements
What do the User Stories mean? Read More »
How do we specify requirements? Chatting is inherently imprecise. Email looses context. Even the ideal requirement document starts to decay once it is done. The most precise way we know to store knowledge is code. Could we use code to write specifications that are easy to understand by non-technical stakeholders and that check the behavior
Executable Specifications Read More »
Our colleague Adi Bolboacă was invited to talk about programming games tonight at xALEc. xALEc is an online meeting for the Agile Lean Europe network where interesting ideas are discussed and exchanged between the community members from everywhere. Programming games are games that programmers can play to improve a specific skill: collaboration, communication, writing expressive
Adi Presents Programming Games Tonight at xALEc Read More »
(Guest blog post by Rebecca Wirfs-Brock, originally appeared on her blog. Republished with permission.) What a busy, intense week Agile 2013 was! It was a great opportunity to connect with old friends and meet folks who share common interests and energy. I also had a lot of fun spreading the word/exchanging ideas about two things I’m
Architecture at Agile 2013 Read More »
Harrison Owen was an ambitious person. In 1983, he tried to organize the best conference ever. After taking care of all details, making sure everything works perfectly and gathering the right speakers and the right people, the conference finally took place. The feedback from the attendees was: the conference was great, but the best thing
What is behind the “Open Space” concept – part 1 Read More »
Often during my life as a programmer, coach and trainer I have to explain how a test should look like. So I decided to write about this subject. Remember that code, especially test code, is read more often than written. Often you will be the person to read it after you wrote it. So do
How an Unit Test should look like Read More »
(Guest blog post by Rebecca Wirfs-Brock, originally appeared on her blog. Republished with permission.) Agile designers embrace change. But that doesn’t mean change is always easy. Some things are harder to change than others. So it is good to know how to explain this to impatient product stakeholders, program managers, or product owners when they ask
Agile Architecture Myths #4 Because you are agile you can change your system fast! Read More »
(Guest blog post by Markus Gärtner, originally appeared on his blog. Republished with permission.) Four months have nearly past since I started my new job at it-agile GmbH. Lots of things have happened since then. I got to know many teams, I learned lots about design, architecture, test-driven development, and also about testing. This blog entry is about
Why is it so hard to teach “what we started to call ATDD”? Read More »
