The Latest
|
Five Steps to Creating Effective Agile Contracts[article] While using an agile approach for projects that involve outside parties can be complex, especially during an audit; living documents and early involvement by all parties involved will help ensure a worry-free process. Learn how expert planning allows for the right path to emerge on its own. |
||
|
The Whats, Whys and Hows of Kanban[presentation] Lean software development practices are gaining momentum-with good reason-and many software teams are learning to use Kanban to help manage development and reduce waste. |
Tim Wingfield, Pillar Technology
|
|
|
Agile Database Development[presentation] If you've had difficulty applying agile methods to the database side of development, you're not alone. Most developers see the database as an obstacle to-not a part of-agile development. |
Pramod Sadalage, ThoughtWorks Inc
|
|
|
Pair Development: How Programmers and Testers Benefit[presentation] Automated tests are a foundation of agile software development. Many experts teach that developers should write unit tests and testers should write higher-level tests. |
Dawn Cannan, 42 Lines
|
|
|
Better Software Conference West 2011: Lean Development Practices for Enterprise Agile[presentation] An enterprise agile initiative requires a higher level strategic, portfolio, product, and team perspective. Lean software development integrates all of these perspectives into a cohesive, actionable whole. |
Alan Shalloway, Net Objectives
|
|
|
The Value of Defining "Done"[presentation] Many agile teams fail to meet customer expectations by releasing products before they are complete. Eric Jimmink coaches teams to treat the Definition of Done (DoD) as a learned and required practice. |
Eric Jimmink, Ordina
|
|
|
Five Dysfunctions of Agile Teams[presentation] Is your agile team not reaching their potential? They may be suffering from internal dysfunctions that contribute to less than optimal results. |
Bob Hartman, Agile For All
|
|
|
Industrial Strength Exploratory Testing[presentation] During the past few years, exploratory testing (ET) has gained popularity as one of the most efficient styles of testing for smaller agile development teams. |
Anutthara Bharadwaj, Microsoft India (R&D) Pvt. Ltd
|
|
|
Product Owner Anti-Patterns[presentation] Do you want a successful product delivery-one that has cost-effective and prioritized product features, that has support from the organization, and acceptance from key stakeholders? |
Monica Yap, SolutionsIQ
|
|
|
Test-driven Development: Achieving Testable Code[presentation] Test-driven Development (TDD) has proven valuable on many development projects for more than ten years. Unfortunately, even today, many teams do not practice it. |
David Yancey, Sogeti, Int
|
|
|
Agile Leadership: Where Do Managers Fit?[presentation] When adopting agile software development, many of the agile roles and practices focus on the team and its members. So, where does that leave the managers-project managers, software managers, IT directors, etc? |
Skip Angel, BigVisible Solutions
|
|
|
Agile Development & Better Software West 2011: Agile Testing: Challenges Beyond the Easy Contexts[presentation] Don't let anyone tell you differently: Agile testing is hard! First, we have to get over the misconception that you don't need testers within agile teams. |
Bob Galen, iContact
|
|
|
Cautionary Tales from Failed Scrum Adoptions[presentation] Although Scrum has become an integral software project management tool in many organizations, not all adoptions have gone well-or as well as they could have. |
Robert Sabourin, AmiBug.com
|
|
|
Virtual Tour of an Embedded Agile Team[presentation] Embedded systems development often includes special challenges: software tightly coupled to rapidly evolving hardware, an end customer with whom you cannot interact, a long period of infrastructure building before any business-value features |
Nancy Van Schooenderwoert, Lean Agile Partners, Inc.
|
|
|
Writing Excellent Executable Requirements[presentation] Many teams build software that does not behave as their customers and users want-and expect. To build the right software the first time, teams need more than written user stories or even detailed specs. |
Eric Landes, Press Ganey
|
Pages
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.