Agile methodologies are helping teams deliver software faster and with much higher quality than ever before.  Given the success of agile at the team level, many organizations are exploring the possibility of implementing agile across the entire product delivery organization.  To help ensure success on a broad scale, there are several critical factors that need to be considered:

• teams should be built around business outcomes in terms of the delivery of working software, not around functional areas or technical silos
• the selection of team members to structure a truly self-contained, cross-functionally complete unit
• the organizational structures, policies and practices that the organization chooses can reinforce learning and lead to sustainable change across the enterprise

Managers at many levels are often concerned about empowering their teams, fearing they may lose control of the project.  In this webcast you’ll hear Certified ScrumMaster, Coach & Trainer, V. Lee Henson, explain the benefits of "letting go" and trusting the team. In addition, Lee will outline the expectations of a responsible, empowered agile team.

Through real-world scenarios and years of project management experience, Lee will discuss:

• The characteristics of an effective agile manager/leader
• The expectations and attributes of an empowered agile team
• The pitfalls and warning signs of a "damaged" team
• The rewards an organization can expect from adhering to basic agile principles.

Building on the principles of PMI® and the Project Management Body of Knowledge (PMBOK), this webcast will explore how a PMP can adapt their knowledge and experience to become an effective agile project leader and:

• Tackle the hidden assumptions behind the PMBOK and explore a more agile approach to managing time, cost and scope.
• Take an in-depth look at the PMI Processes and Knowledge areas and explore how to adapt them to agile projects.
• Gain a new way of thinking about project management best practices and new tools to deliver value in the face of uncertainty.

Join Jeff Sutherland, Ph.D., Certified ScrumMaster Trainer and Co-Creator of the Scrum development process and Ian Culling, CTO, VersionOne as they share their insights about extending a successful agile pilot project across a development organization and scaling large agile deployments. Specifically, learn how to avoid these five sure-fire ways to fail at scaling:

• Skimp on training and education
• Practice agile in silos
• Ignore other areas of the business
• Encourage organizational complexity
• Fail to scale the infrastructure

This presentation explores how agile teams estimate and plan, what these teams measure, and how these metrics can be used to manage project performance. Additionally, this talk covers:

• Four key agile concepts: story points, velocity, defect trend and burndown
• How these agile metrics can be used to deliver graphically rich, accurate and timely project reporting

Listen to two of VersionOne’s premier Agile consultants tackle tough questions about how an agile approach impacts the role of the Business Analyst including:

• What differentiates traditional requirements management from agile requirements management?
• What does agile mean for the BA?
• What new skills does a BA need to learn?
• How does agile development change the relationship between the BA and the customer (or the team)?
• What can BAs do to be more agile if they are working in a more traditional environment?

Two of VersionOne's very own experts present a high-level overview of Lean/Kanban principles followed by a demonstration of the new Storyboard feature in the latest release of Enterprise Edition.

First, David Laribee, VersionOne Agile Coach, will guide a Lean/Kanban discussion covering one-piece flow, pull systems, continuous improvement and will delve into some of the Lean tools software teams can use to manage work and improve their practice.

Andy Powell, Sr. Product Specialist, will then demo the latest release of VersionOne's Enterprise Edition, specifically looking at the Storyboard, Work in Process (WIP) limits and cycle time reporting that support distributed teams who are using Kanban and other Lean approaches.