DURATION: 1 DAY
WHAT DOES IT MEAN AND WHAT DOES IT INCLUDE?
In most of the papers, agile frameworks like SCRUM replace the “Project Manager” by other roles. This works well for different industrial areas but in some this is a challenge to do so. Major reason here fore is, that there are still parts in the development, which must run in a traditional way. There are different opinions about how to merge the traditional and agile frameworks together.
Primary we would like to give you an overview of the differences of major attributes in traditional and agile working models . Step by step we work together on how to solve the challenges in short, middle and long-term planning. Aspects during the execution phase (e.g. tooling, processes, methods) and how to handle the continuous development. We build on recommended theory and work together on the practical day to day seen situations and examples.
GOALS IN ATTENDING THIS TRAINING
We assume you have many open questions in your mind, which you carry with you day to day. This list of questions getting more and more…
"Who is taking the role of the project manager in SCRUM?"
"How can I set a scope for an agile project, if I do not know the long-term goals?"
"Since we started working agile, I do not have any time for reporting anymore. Is reporting still important?"
"Sometimes I have the feeling to be in meetings all the time. And now all those dailies.
Is there an efficient way for this?"
Let us understand the standard and find in practical examples the answers to your day to day questions.
AM I THE RIGHT ONE TO ATTEND THIS MODULE ?
Did you attend our training module A? If yes than the first step is done to be the right one for this session. Are you in charge of the roles as Management, Sales, Quality, Process Development, Project Management or you are selected as a SCRUM Master and you have a bunch of questions about “AGILE” or “AGILE vs traditional”? We think exactly you are the right one to attend this session.
A ROUGH OVERVIEW OF THE AGENDA
Comparison of different working models (traditional, agile)
Product vision and Backlog (including estimation)
Release Planning based on the vision and the velocity
Agile adaptive planning
Transparency using events and artifacts of agile frameworks
Synchronization with stakeholders