The Latest
|
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 |
Dan Rawsthorne, CollabNet
|
|
|
Project Governance vs. Agile Flexibility[presentation] Organizations use project governance to control a project’s activities-scope, cost, schedule, activities, personnel, quality, and authority. |
Mario Moreira, CA Technologies
|
|
|
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. |
Fadi Stephan, Excella Consulting
|
|
|
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. |
Sanjiv Augustine, LitheSpeed, LLC
|
|
|
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. |
Griffin Jones, iCardiac Technologies
|
|
|
Ten Great Practices Learned from Open Source Projects[presentation] Open source development combines distributed teams, resource constraints, and an overload of end user input. |
Mik Kersten, Tasktop
|
|
|
User Stories from MONOPOLY: Complex Rules, Random Events, and Twisted Exceptions[presentation] Agile developers often face the difficult task of defining user stories from business rules for complex applications-medical, embedded, insurance, banking applications, etc. |
Robert Sabourin, AmiBug.com
|
|
|
Designing Agility that Lasts[presentation] Every day more agile practices and styles emerge, overlap, and complete. This proliferation challenges you to choose from among XP, Scrum, Lean, Kanban or the ways of the Lean Start Up crowd. |
David Hussman, DevJam
|
|
|
Test Specialist on Agile Teams: A New Paradigm for Testers[presentation] As a tester on an agile team, are you still creating lots of scripted test cases the old way? Are you still caught in the classic waterfall-always behind-while the rest of the team is doing Scrum and looking forward? |
Henrik Andersson, Jayway - Test
|
|
|
Continuous Integration: Sign of a Great Shop[presentation] Relentless automation is the sign that your software team has discovered how valuable their time is and how much of their day can be wasted performing trivial tasks. |
Jared Richardson, Logos Technologies
|
|
|
INVEST: Agile Requirements that Tell a Story[presentation] Unlike traditional requirements-formal specification documents produced mostly up front-agile requirements are elicited and recorded in smaller units-called stories or user stories that are generated quickly with a just-in-time approach. |
Ken Pugh, Net Objectives
|
Pages
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.