About Agile-Minds – www.agile-minds.com
Agile-Minds is my site about experiences I made with agile product & software development. It talks about the gains and challenges of agile methods like SCRUM, KANBAN and the LEAN principles, discusses challenges from the domain of product development and solutions that worked for me. The site is public – but its main purpose is to be a notebook for myself where I pencil down insights and learnings for further usage.
The site contains information about agility and how it impacts your daily business life. Agile software development practices changed the way we built software. Agile product development ensures continuous availability of changes for our customers. LEAN principles helped us to put the software and product development methods together and showed us a way to control our business with agile methods working under the hood. LEAN methods came with “avoid waste”, “validated learning” and the “build-measure-learn” cycle defined by Eric Ries in “The LEAN Startup | Methodology”.
Agility can go even further. If the organization allows to revert the PUSH-principle into a PULL-principle – it empowers people to change a whole business organization. The fundament for an organizational transformation.
About me – Michael Maretzke
Currently, I am serving as COO @ gutefrage.net. gutefrage.net is the #1 question and answer platform in the german spoken region – from users for users.
The COO role includes the responsibility for product management, software development, SEO and agile methods.
Previously, I worked as CTO @ FriendScout24 – now better known as “LoveScout24”. FriendScout24 is still the leading online dating web site in Germany, Austria and Switzerland.
As the CTO I worked together with a team of ~40 people. In 2010, we introduced SCRUM as our agile software development method. Along with 3-week sprint cycles we made our way through all the ups and downs. End of 2011, we moved from 3-week cycles to 2-week cycles – creating quite some pain. Moreover, beginning 2012 we moved even further – switching from SCRUM to a flow-based software development process managed with KANBAN. Mid 2012, we arrived at daily deployments and continuous delivery.
We run on-site teams, mixed-teams with people on-site and off-site, teams working on product features, maintenance teams, teams working on web-portals, teams producing native applications.