2014 was a great year for me. I've helped organization to effectively deploy Agile and Lean and improve their ways of working, my first book became a bestseller and I've inspired professionals all around the world by sharing useful knowledge and experience on my blog and via InfoQ. Let's reflect on what 2014 has brought and do a futurespective to visualize the opportunities of 2015.
When an organization is experiencing quality problems with their products, agile software development often isn't the first solution that comes up in people's minds. Often I see people trying to address them using classical waterfall based approaches, only to find out that it will make problems even worse. I recommend agile, not only to deliver working software faster but also with the right quality. This posts shows how empowering the team helps to increase the quality of product.
To deliver high-quality products to customers, agile quality practices have to engrained throughout development. It all starts with ensuring the quality of the requirements.
Root Cause Analysis can be used in software development to build a shared understanding of a problem to determine the first or “root” causes. Knowing these causes helps to identify effective improvement actions to prevent similar problems in the future. You can also do Root Cause Analysis in agile to stop problems that have been bugging your team for too long.
Agile promotes that teams work in a sustainable pace, delivering value for their customers. When teams are working under too much pressure, technical debt will increase and velocity of teams will go down. Agile retrospectives can help you to discover the causes of pressure, and to take actions to reach a sustainable pace with your teams.
The book The Clean Coder by Robert C. Martin is about attitude and discipline in software development. Robert explores how soft skills matter in IT, how people communicate and collaborate and develop their skills to become a professional programmer.
Wat kan Scrum doen voor de kwaliteit van producten en diensten, en hoe kan samenwerking met de gebruikers zorgen voor een betere kwaliteit?
The book Economics of Software Quality provides solutions to quantify Software Quality and manage software development and maintenance. It contains data usable to build a business case to improve quality, and decide upon improvements in your organization.
De gastblog van Christophe Vroom beschrijft wat eHRM kan betekenen voor medewerkers, en geeft enkele aandachtspunten voor de implementatie van eHRM.
I’m an Editor for Agile on InfoQ, covering news on topics like Agile Adoption, Culture, Lean, Agile in the Enterprise, Governance, Measurements, Coaching, Collaboration, Teamwork, Professionalism, Feedback, Continuous Improvement and Lean Startup. And I will also be doing interviews, book reviews, articles, and coverage of conferences.
How can you manage projects with the agile approach, using user stories, planning games, and a flexible scope?
What are the needs of the business and customers for process improvement? With solutions to find better ways to do process improvement!