Once you are introduced to an Agile Framework, it is a common practice to refer to Waterfall methods as the outdated and senile grandfather, but at the same time blaming the parent organization for lacking the right "Agile mindset" or that SCRUM isn't enough for real-life scenarios.

Here we ignore the common mistakes that made the traditional Project Management fail and how we are simply re-packaging it more often than actually going through the shift of imbibing the mindset transition required.

We still have resource planning, utilization monitoring and people management to be done. But with no Project Managers - how do we respond to this data. Most people continue older methods assuming Agile doesn't address these situations. I would like to talk about how we can be more "Agile" with our "management"

Once you are introduced to an Agile Framework, it is a common practice to refer to Waterfall methods as the outdated and senile grandfather, but at the same time blaming the parent organization for lacking the right "Agile mindset" or that SCRUM isn't enough for real-life scenarios.

Here we ignore the common mistakes that made the traditional Project Management fail and how we are simply re-packaging it more often than actually going through the shift of imbibing the mindset transition required.

We still have resource planning, utilization monitoring and people management to be done. But with no Project Managers - how do we respond to this data. Most people continue older methods assuming Agile doesn't address these situations. I would like to talk about how we can be more "Agile" with our "management"

Once you are introduced to an Agile Framework, it is a common practice to refer to Waterfall methods as the outdated and senile grandfather, but at the same time blaming the parent organization for lacking the right "Agile mindset" or that SCRUM isn't enough for real-life scenarios.

Here we ignore the common mistakes that made the traditional Project Management fail and how we are simply re-packaging it more often than actually going through the shift of imbibing the mindset transition required.

We still have resource planning, utilization monitoring and people management to be done. But with no Project Managers - how do we respond to this data. Most people continue older methods assuming Agile doesn't address these situations. I would like to talk about how we can be more "Agile" with our "management"

Most people struggle with real-life scenarios that seem to make Agile look un-realistic and blame other people or processes for the failures.

I'll go through some of these most common scenarios - talking about what we do wrong and how we can overcome such challenges using SCRUM values.

To help my case - I will be taking 3 case studies that cover some frequently encountered scenarios and take a deep dive on how we can better respond to such situations and events.

Most people struggle with real-life scenarios that seem to make Agile look un-realistic and blame other people or processes for the failures.

I'll go through some of these most common scenarios - talking about what we do wrong and how we can overcome such challenges using SCRUM values.

To help my case - I will be taking 3 case studies that cover some frequently encountered scenarios and take a deep dive on how we can better respond to such situations and events.

Most people struggle with real-life scenarios that seem to make Agile look un-realistic and blame other people or processes for the failures.

I'll go through some of these most common scenarios - talking about what we do wrong and how we can overcome such challenges using SCRUM values.

To help my case - I will be taking 3 case studies that cover some frequently encountered scenarios and take a deep dive on how we can better respond to such situations and events.