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.
At the recent Agile 2016 Conference, leadership expert and author Steve Denning presented a fishbowl-style session focused on the topics of Agile within Large Organizations and Leadership in Agile. He covered three broad topics: Engagement of Leaders - Agile Mindset Shift in Management, Agile Adoption Challenges and Agile in the Global Economy
When organizations are growing fast it can be a challenge to keep them sane and to achieve what you actually want to achieve by hiring more people: getting more done. Alexander Grosse talked about how you scale teams to build an effective organization at Spark the Change London 2016. He explored the five domains of scaling teams: Hiring, People Management, Organization, Culture, and Communication.
David Horowitz and Mark Kilby presented at the Agile 2016 conference on how distributed teams can thrive. The premise of their talk was that distributed teams need to be connected, and that while face-to-face is important for collaboration, it isn’t as important as connectedness.
The Agile 2016 conference annual Industry Panel Discussion session examined Agile Trends and Future Directions. The panel discussed the implications of artificial intelligence and machine learning on the software industry, safety and ethics in AI systems, whether the Agile Manifesto should be updated, and the impact of tools on agile adoptions.
During his presentation at the Agile 2016 conference, Mike Cottmeyer focused on leading large-scale agile transformations. He specifically discussed how to talk to executives about this transformation and ensure that the transformation is measured and set up in the mindset in which executives will respond.