Scott Hanselman advices on dealing with information overload: audit and sort info sources, schedule work sprints, turn off distractions, triaging the inbox, having a personal toolbox.
Dan North engages the audience into a discussion about the tradeoffs involved in making decisions regarding the team composition, development style, architecture, and deployment solutions.
Jurgen Appelo discusses introducing change inside organizations by viewing them as adaptive systems and social networks and using the Change Management 3.0 model.
Russ Miles and Toby Hobson outline many factors to be considered when adopting a cloud solution – what type of cloud, which vendor, what technology, how is it related to the business value, SLA, should it be considered early, geo-location constraints, etc. –, creating a wider view of the cloud from the development and business perspective.
Alan Chedalawada discusses Standard Work as a solution for software organizations adopting Lean by discovering and applying the best approaches, by continually improving the standards, by involving everyone in the organization – business, management, technical team – to participate in standards’ improvement, by preserving the knowledge gained over time.
Agile came from small, colocated projects in the 1990s. It has spread to large, globally distributed commercial projects, affecting the IEEE, the PMI, the SEI and the Department of Defense. Agile now sits in a larger landscape and should be viewed accordingly. This talk shows that landscape, clarifying how classical agile fits in and what constitutes effective development outside that narrow area.
This presentation explores how the role of managers changes in Scrum. It helps managers to lead the introduction of Scrum acting as role models. It presents leadership principles that provide concrete guidance such as servant-leadership, empirical management, empowerment and respect, quality-first and continuous improvement.
Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD). The presentation intends to be a primer for managers who want to understand the value of TDD, and of Agile in general, in software development.
Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.
Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, former Chief Engineer at Toyota, and the lessons he learned from him.
In this presentation, recorded at QCon, Burton Group research director Anne Thomas Manes talks about how to make the business case for SOA. Her talk covers explaining SOA to non-technical business people, various approaches for selling SOA to management and gaining funding for SOA investments.
Of course, "anything more than 'barely sufficient' process is waste," but what does that mean for your team, or my next project? In this 60 minute presentation from the APLN Leadership Summit at Agile2006, Todd Little shared a model to help choose the right "flavour" of Agile for different kinds of projects, and discussed the importance of 'steering' throughout the project's duration.