Much software and systems development involves a complex mix of people, teams, technologies, skills, architectures, and organisational structures that must all interact for initiatives to achieve their goals. However, many organisations struggle to scale up agile approaches for their various programs, products, and services.
Configuring jobs is the bread-and-butter of Jenkins. However, tracking their subtle differences can be hard. The configuration of jobs can become outdated or incomplete. While there are many plugins that can help with this, none of them solve the full scope of the problem.
Complex software always has an architecture, even if it isn’t intentional. Being agile isn’t enough. It isn’t prudent to just keep your code clean and hope that good architecture will simply emerge. Especially when there is a lot of technical risk, interdependencies, and conflicting priorities. Good architecture requires ongoing attention …
Have you ever wondered if there was a better way to learn refactoring? Martin Fowler’s Refactoring book was a great introductory book on how to clean up legacy code bases, but over the years, what I have found missing in that book is one a set of guidelines that links …
The hardest part of big projects is that they are BIG. Of course “big” means different things to different people. What some measure in cash, others measure in technology. Little value flows when we focus on the number of people “doing agile.” Big value is more likely to flourish when …
Learn the principles and practices of scaling Agile teams beyond Scrum of Scrumsa nd see how they work together to address coordination, integration, and technical integrity without adding levels of hierarchy or bureaucracy.
