Page 1 of 1 — 9 articles
There’s a lot to unpack when working with an agile agency or advocating for agile at your own company. To an untrained eye, agile ceremonies might look like an overhead. Two of them - review and retrospective - have synonymous names. It doesn’t help your case.
Read the articleIf you had to differentiate between agility and “Agile” (with a capital “A”), how would you explain the difference?
Read the articleAgile is a peculiar methodology. It's scary to trust the process when you have to jump into your first project without a fixed budget. But Agile isn’t devoid of estimates.
Read the articleThere’s one particular principle in the Agile Manifesto that makes eyebrows rise when you hear “agile” and “planning” in the same sentence. Agile is all about continuous improvement and delivery. It values communication over documentation and tackles issues “as and when needed”. Is there a place for planning in such an environment?
Read the articleTechnical debt is a metaphor for the shortcuts that we take in software development. In the same way that financial debt can be useful when it helps you to achieve your goals quicker, technical debt can make sense when it enables you to get something working quickly. These shortcuts come at the cost of increased development effort in future releases—effort that may be impossible to predict, but which can often be significant.
Read the articleIn agile, velocity is a concept which refers to the amount of work that has been done during an iteration. It’s a measurement that tracks information about work completed, work started, and work remaining. Velocity is considered to be one of the most important metrics in agile. Not only does it allow you to track progress, but it also helps deliver the most value.
Read the articleWhat is a user story? Why write it? Who writes? What is a good example of a user story? Are there any exceptions? In this article, I focus on an in-depth analysis of writing user stories from different angles.
Read the articleWebsites have evolved drastically in just a few decades. They went from being a novelty to something that “every business needs”. But there’s one thing that didn’t keep up with that rapid evolution - the process of designing and developing websites. Most agencies build websites the same way they built them 20+ years ago.
Read the articleBuilding products for months using a traditional, linear approach is holding businesses back. Your company changes all the time and so do the requirements. Locking in a fixed scope for a website always ends in a tug of war. The scope evolves with your business and by the end of the project the initial requirements are outdated.
Read the article