The Latest
Focus on Value First: An Agile Transformation Competency Framework[presentation] Organizational transformation is difficult work. Many agile transformation efforts begin with lofty goals only to be sabotaged by unrealistic expectations about the depth and complexity of the changes required. |
Tamara Runyon, CollabNet
|
|
Lean Framework, Agile Principles, and CMMI®[presentation] Many large software development organizations, which have discovered that they must become more agile to compete, frequently ask Dan Rawsthorne, "What does 'big' scrum look like?" Because no two organizations are alike, this simple question d |
Dustin Potts, Nationwide Insurance
|
|
Development Productivity: The Science behind Motivation[presentation] When there is a defined task with a clear set of rules to follow, rewards are an excellent way to encourage desired behavior. |
Russell Pannone, We Be Agile
|
|
Dealing with Stories: Sizing, Tracking, and Defining "Done"[presentation] For story estimating and tracking, Ken Pugh finds the same issues seem to crop up on many teams-whether a story is too big, too small, or just right; how best to track stories; the definition of “done” for a story; and what should be represen |
![]() |
|
Agile Pathologies: People Problems in Agile Shops[presentation] For agile adoptions that fail, you may not be sure of what went wrong or exactly where but you know something is broken somewhere. And with success, you often do not know what went right. |
Rajeev Singh, ThoughtWorks Inc
|
|
Agile Development Conference & Better Software Conference East 2011: Patterns of "Big" Scrum[presentation] Nationwide Insurance, one of the largest insurance companies in the United States, is the home of a next generation application development lifecycle fusing a lean software development framework with agile principles and techniques within a C |
![]() |
|
Project Governance vs. Agile Flexibility[presentation] Organizations use project governance to control a project’s activities-scope, cost, schedule, activities, personnel, quality, and authority. |
![]() |
|
Software Craftsmanship: It's an Imperative[presentation] Sadly, ten years into the evolution of agile practices, many teams fail to learn and implement the software development practices that are necessary for long-term code quality and agility. |
![]() |
|
Scrum vs. Kanban: It's Not Necessarily All of One or the Other[presentation] Have your Scrum development teams discovered that grooming some features only one sprint ahead is too late? |
Season Tanner, State Farm Insurance Companies
|
|
Eight Principles for Better Unit Testing[presentation] Unit testing is a core component of agile development methodologies. Teams that perform comprehensive unit testing are perceived to be more reliable, professional, and advanced. Yet, many developers find starting unit testing is difficult. |
Gil Zilberfeld, Typemock
|
|
Agile Development on Large Legacy Architecture[presentation] Twenty years of traditional processes produced valuable applications at Integrated Research (IR). However, making changes to software was slow and often introduced quality problems that took months to resolve. |
Tony Young, Integrated Research
|
|
Agile Requirements Readiness ... and the Role of Testers[presentation] Mature agile teams work together to ensure sufficient requirement information is ready when an iteration starts. |
Christopher Duro, Cognizant
|
|
Agile Development Conference East 2011: The Agile PMO: From Process Police to Adaptive Governance[presentation] Although success stories from individual agile teams on single projects abound, agile adoptions encounter significant challenges scaling to multiple teams on multiple projects. |
![]() |
|
Surviving an FDA Audit: Heuristics for Exploratory Testing[presentation] In FDA regulated industries, audits are high-stakes, fact-finding exercises required to verify compliance to regulations and an organization’s internal procedures. |
![]() |
|
Ten Great Practices Learned from Open Source Projects[presentation] Open source development combines distributed teams, resource constraints, and an overload of end user input. |
![]() |