scaling agile
|
For Programs, Short Is Beautiful Johanna Rothman describes that for programs, since you have many teams, you want shorter iterations and small stories in order to make sure you have as many interconnection points with the rest of the feature teams as possible.
|
|
|
Disciplined Agile Delivery in IT: A Full Lifecycle Approach
Slideshow
The good news: Agile methods deliver superior results compared to traditional approaches. The bad news: For IT projects, mainstream agile methods-Scrum, Extreme Programming (XP), and Agile Modeling (AM)- provide only part of the overall solution. Agile IT projects require some time and effort for upfront planning at the start and activities for sophisticated deployment scenarios at the end. Additionally, most agile projects in large IT organizations cannot escape compliance with governance standards. Mark Lines describes and explores the realities of agile development in enterprise IT environments. Discover how IBM’s freely available Disciplined Agile Delivery (DAD) process framework combines common practices and strategies from mainstream agile methods to address the full delivery lifecycle-from project initiation to solution release into production.
|
Mark Lines, UPMentors
|
|
Agile Architecture Practices for Large Scale Agile Development Although “agile architecture” may sound like an oxymoron to you, the reality is that a simple, elegant architecture is a key enabler of any successful system, particularly large scale ones. Scott Ambler describes agile architecture practices-at both the project and enterprise level-that form a middle ground between the extremes of big architecture up-front and outright hacking. Scott discusses agile modeling practices-initial architecture envisioning, proving an architecture with working code, and just-in-time model storming-that enable agile teams to benefit from architectural modeling without suffering the drawbacks of detailed design documentation. Beyond architecture, Scott introduces agile design techniques-continuous integration (CI), test-driven development (TDD), and refactoring-that build on and provide feedback to an emergent architecture.
|
Theresa Quatrani, IBM Rational
|
|
Performance Testing Throughout the Life Cycle Even though it is easy to say that you should continuously test your application for performance during development, how do you really do it? What are the processes for testing performance early and often? What kinds of problems will you find at the different stages? Chris Patterson shares the tools and techniques he recently used during the development of a highly concurrent and highly scalable server that is shipping soon. Chris explores how developers and testers used common tools and frameworks to accelerate the start of performance testing during product development. Explore the challenges they faced while testing a version 1 product, including defining appropriate performance and scale goals, simulating concurrent user access patterns, and generating a real world data set. Learn from his team's mistakes and their successes as Chris shares both the good and the bad of the process and results.
|
Chris Patterson, Microsoft
|
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.