Per the Agile Business Consortium, business agility allows businesses to adapt quickly to market changes; respond rapidly and flexibly to customer demands; adapt and lead change in a productive and cost-effective way without compromising quality; and continuously be at a competitive advantage. The primary reason for moving to Agile is to achieve faster business value and keep you ahead of the competition. Agile is built for change - fundamentally, it is about creating Business Agility. It enables the enterprise to deliver projects more efficiently, with relentless focus on business value and providing the highest return on investment. Whether it is a software project, a new service offering or a new product, Agile’s twelve principles and three pillars (transparency, inspection, adaptation) are designed to reduce money spent on undesirable or unusable features which were built based on outdated requirements.
9 items found
Coordinating Knowledge Work in Multiteam Programs: Findings From a Large-Scale Agile Development Program
Software development projects have undergone remarkable changes with the arrival of agile development approaches. Although intended for small, self-managing teams, these approaches are today used for large development programs. A major challenge of such programs is coordinating many teams. This case study describes the coordination of knowledge work in a large-scale agile development program with 12 teams. The findings highlight coordination modes based on feedback, the use of a number of mechanisms, and how coordination practices change over time. The findings can improve the outcomes of large knowledge-based development programs by tailoring coordination practices to needs over time.
Where should you use Scrum and where should you use Kanban? Many factors weigh into this decision, including whether your teams are in development or maintenance mode and whether their work is highly predictable or sporadic. Attendees of this webinar will come away with a better understanding of Scrum and Kanban and when to utilize each, together or separately, to improve agility of their teams.
The concept of the Agile Project Manager is almost universally accepted, at least in IT projects; although there is no Agile Project Management Methodology. Traditional approaches like PMBoK and PRINCE2 had always the capability to use techniques that are part of the Agile delivery: incremental and iterative development, early delivery of increments of the project, multi-functional teams, inspect and adapt, etc.
For the past 15 years, the Scrum Master and Project Manager roles have coexisted well, especially in IT projects. From the very technical role that was part of the Software Development Team, the Scrum Master evolved into a new organizational role sometimes with a well-defined job description and with responsibilities that transcended the technical background from which it originated. Although the role was defined in the Scrum framework, the Scrum Master role is now present in other frameworks
Project Managers will continue to play a vital role in the new Agile world. At the Enterprise Level there will always be a need for Governance and the larger the organisation, the more focus there will be in managing risks.
Six Sigma can be the balance between Lean and Agile, measuring the impact of Lean and/or Agile initiatives. This presentation is based on a real case study, using Lean Six Sigma's Define, Measure, Analyze, Improve, Control (DMAIC) process to make the Scrum process more efficient in a software start-up.
Just because you are working in a waterfall organization doesn't mean you can't be Agile. Join Dave Prior as he walks you through a case study on implementing Scrum in a waterfall environment. He offers some key practices and data points that will enable you to be successful in both keeping the team productive and providing the information needed to build trust and confidence with the Project Sponsors and Senior Executives you need to support your Agile implementation.