|
Below is a photo of an agile team working. It is a great example of knowledge work. Compare it with a manufacturing work on the photo below. The knowledge work goes on inside a developer's head. This makes it difficult to intervene if a developer needs help on the...
Jason Yip explains really well many concepts for delivering faster. He has some really cool drawings. Well done!
Similarly to Test Driven Development (TDD)--Writing tests before code--, my current team is following a Toggle Driven Development: Writing toggles before code. The main point is: if you are using toggles, consider designing/creating/refactoring the toggle strategy...
I have been running retrospective activities for a long time. I really like retrospective activities. Interesting enough, I have not married with one activity. I try new activities. I brag to my friends about the latest one. Many times I repeat old ones. But I do not...
Agile software development is typically iterative and incremental. The software requirements are sliced and planned into iterations. The software is built incrementally, with newly developed slices being added to (or deployed with) the working slices. The figure...
Software development is empirical, hence you need processes and practices that allow the team to adapt to circumstances, and effectively work with Software development and its empirical nature. To this end, Agile shifts the focus from heavy planning and repeatability...