Software architecture — The Hardest parts, and how to live with them
I recently read the book “Software Architecture — the Hard Parts”. In this three-part series of articles, you have my top 4 list of the hardest parts and six patterns that I’ve found useful. In this part I'll introduce six patterns that I’ve found useful when struggling with these vicious problems.
Software architecture — The Hardest parts - Part 2 of 3
I recently read the book “Software Architecture — the Hard Parts”. In this three-part series of articles, you have my top 4 list of the hardest parts and six patterns that I’ve found useful. Let's continue with the top 2 from my top 4 list.
Software architecture — The Hardest parts - Part 1 of 3
I recently read the book “Software Architecture — the Hard Parts”. In this three-part series of articles, you have my top 4 list of the hardest parts and six patterns that I’ve found useful. Let's start with the bottom two from my top 4 list.
Are you happy with crappy estimates? — Patterns and practices for better estimates
The estimates are a tricky thing. There are a lot of good estimation techniques, but no technique is perfect. There is also a lot of polarized debate about software estimation. I’ll try to avoid that and shed a systemic view on the topic. Here you have my top 12
Productive Remote Teams Interactive Webinar: Remote retrospectives
"People are passive", "Clumsy tools", "Lacking human connection"... These are all common challenges agile coaches, ScrumMasters and facilitators face when facilitating retrospectives remotely. At Flowa we have run Remote retrospective for years because we are located in Helsinki and Jyväskylä. We have also experience
Remote patterns and practices: Pizza co-writing
One of the problems we have come across is how to effectively produce content together. Pizza co-writing is our favorite method for this.
Remote patterns and practices: Weekly goals
Weekly goals practice is about choosing tactics that support strategy and collaboration and guides day-to-day work. Weekly goal ideal for seasoned self-organized teams and small organizations.
Build business, not features!
“If you release and you’re not embarrassed, you're too late”, I’ve been repeating. We experimented if we are practicing what we preach.
How to break 4 vicious cycles of software development
At Flowa we have seen quite a few software projects over the years, and worked with dozens of organizations having software in the core of their business. We have identified 4 common vicious cycles and ways for breaking them. 4 vicious cycles of software developmentWhen we work in a customer
Tracking raw materials with blockchain - enabling climate impact and carbon accounting
The Earth loves transparency! It allows us to fight climate crisis effectively. We need transparency to ensure that the burden of the needed climate action is shared fairly and there are no freeriders. Then again, there are dozens of layers and business owners who are afraid of transparency. Too much