Scaling Agile practices beyond software development teams and IT departments is a growing trend, and the Agile Enterprise is a reality rather than a goal. However, the transition from planned approach to Agile is a painful change, and PMO can provide support for Agile rather than be perceived as an archaic team supporting “waterfall”. Once the organisation decides to adopt Agile, the PMO should be the champion of the transformation process, providing support to the Project Managers with less experience with Agile delivery while ensuring that governance requirements are met. This webinar is a summary of the presenter’s experience in organisations transitioning to Agile.
143 items found
Predictive, Iterative and Adaptive Life Cycle Approaches: Managing Projects in the Knowledge Environment
While the number of project management frameworks (COBIT, PMBOK, PRINCE2, SCRUM, SAFe) continues to increase, the number of approaches to project management used by organizations and practitioners appear to be decreasing. Although other useful approaches to managing projects surely exist, many publications now promote the use of two (2) primary approaches - Predictive and Agile.
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
This webinar is a review of the principles and concepts developed before the publication of the Agile Manifesto and an analysis of the evolution of Agility in the last 25 years.
Agility continues to be a highly discussed subject. The success of using Agile approaches, mainly Scrum or similar frameworks, has organisations and managers thinking of replicating its success at the department level and even at the organisation level. This webinar looks at Agility at the Enterprise level from a Project Manager perspective, explaining the difference between the new Agile Enterprise (a top down Agile approach) and Enterprise Agile (the bottom up Agile transformation) that is scaling popular Agile frameworks from team level to organisation level.
Have you or your Agile teams had trouble refining requirements on an Agile project? Are your teams struggling with user stories and tasks that are too large for them to handle well? If so, you and your teams need more guidance to implement backlog / user story grooming. Backlog grooming is a step-by-step process of taking high-level (“coarse-grained”) requirements and refining them to lower-level user stories and tasks (“fine-level”) that are ready to put into a sprint. In RefineM’s Backlog/Story Grooming presentation, attendees will learn how to work the process to achieve fine-grained requirements that are ready just in time. The key to success is leveraging tools and techniques as well as the expertise of your team to refine requirements iteratively.
Lean Six Sigma techniques can be used at a smaller scale, but to be successful it needs to be adapted to the specifics of IT projects. This presentation is based on a real case study, using Lean Six Sigma to measure the impact of process improvement initiatives in a hybrid project delivery environment.
Hearing all the buzz about agile, wondering how you can get in the game? There are many ways to gain the benefits of Agile – from full on methodology to a hybrid approach. If you not ready to pick a method, but still interested in how you can use components of Agile, then this webinar is for you.
Business Analysts, or those performing this role, have created Business Requirements Documents (BRDs) for many years. This was often done in the early stages of a project, documenting very detailed requirements that were often considered “frozen” because of the complexities and effort to produce them. The Agile world has turned the role of the business analyst upside down.