At the recent Agile 2016 conference, InfoQ spoke to Kyle McMeekin about the real world challenges around software testing in agile development, the push to have more test automation and how exploratory testing is different from and more effective than scripted manual testing.
People are hardwired to instantly decide who we trust, but also to work collaboratively in small groups. Cognitive biases can get in the way of collaboration, but when you understand how these biases work and what agile practices can do to help, you are more likely to build better interpersonal relationships and create successful products.
Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.
To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.
Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.
Scalability should be considered when developing a Minimum Viable Product (MVP). An MVP needs to be technically scalable and you need to have a plan on how to scale quickly when your MVP attracts many users and becomes successful. Knowing your possible performance bottlenecks and using common sense while developing your MVP will get you very far, says Erik Duindam, CTO at Unboxd.
If you want continuous improvement you can start with retrospectives, but you must go far beyond that with change management, culture change, and innovation. The most important thing in order to make change happen in organizations is creating new habits and changing your culture.
Bias, priming, and salience are the main psychological factors that influence our ability to estimate. Knowing what happens psychologically when we estimate, and using techniques from psychology, helps us to deal with those factors so that we can improve our estimations argued Joseph Pelrine, social complexity scientist and PhD researcher in psychology.
The Agile Alliance hosted a one-day Executive Forum in San Jose, CA on September 19. The event attracted participants from around the world and a range of senior speakers from large organisations, and focused on how adopting agile development impacts companies and what executives need to do to help ensure successful cultural transformation, which is what agile adoption at scale is about.
When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.
People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.
At the recent Agile 2016 conference Lee Cunningham, VersionOne’s Senior Director of Enterprise Agile Strategy, spoke to InfoQ about scaling agile, expanding agile beyond IT, identifying value and the direction of the VersionOne platform.
Continuous deployment results in a higher sense of responsibility and better quality of deployments, argues Paul de Raaij, technical pathfinder at Coolblue. Coding standards prevent your code base from becoming a mess, automated inspections are great for tedious and boring checks, and manual checks are great for checking if the logic or use of code actually makes sense.
Good engineering practices are the tools that help agile teams to deliver shippable products. Although many engineering practices have proved to be effective, they are not as widely used as they should be. Agile anti-patterns like the software testing ice-cream cone, accumulating technical debt and functional silos prevent teams from delivering a potentially releasable product.
At the Agile 2016 conference Andy Hircock, Mike Lowery, and Rob Vandenburg, discussed how they transitioned to persona-based teams, instead of feature or component based, and how they used this to help teams keep focused on their customers despite significant growth.