Are you a business analyst who wonders how you can use your business analysis capabilities to be competitive in the job market for the next 3 to 5 years?
As I first noted back in 2017, product owner and product manager roles offer a viable career path for business analysts, especially those who currently work on custom software development projects.
Come to this session to learn about the similarities and differences between business analysis, product owner, and product manager roles. Then discover how you can apply your business analysis experience to becoming a product owner or product manager. Along the way, you’ll hear about the lessons I and others have learned from moving from business analysis through product owner to product management roles.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
Objective
• Understand Agile software development
• Difference between Waterfall and Agile methodology
Agile Manifesto
Agile Benefits for Business
Agile Benefit for Developers
• Agile Umbrella
Scrum - Framework
Things we do in Scum
Scrum Team
User Stories
Prioritization - MoSSCoW
Sprint – Planning Meeting
Daily Scrum Meeting
Sprint Review Meeting
Sprint Retrospective
Scrum Values
• Tool to manage Agile Teams
Jira Software
Scrum is an iterative and incremental agile software development framework for managing product development. Diceus is following this methodology in various of projects, which give us and our clients invaluable advantage during development life cycle. The result of this approach is always stable and successful product.
You could find more information about Scrum methodology and Business Intelligence in our blog:
http://blog.diceus.com/
How to Build a Product Roadmap by eBay Director of ProductProduct School
Sudha Mahajan talked about how to build great roadmaps! Great roadmaps require right trade-offs, right prioritization, strong execution rigger and above all success metrics. A strong roadmap is your channel to success. There is no one size that fits all, but there are certain techniques that can help you get there.
Learn more about the most popular Agile framework - Scrum. This training should be paired with the pre-training learning materials in Trello. Learn more about the Scrum artifacts (product backlog, sprint backlog, etc.), Scrum roles (Scrum Master, Product Owner, and the team), and the Sprint.
What does a Scrum Master do all day if a Daily Scrum is only 15 minutes? This talk - “A Day in the Life of a Scrum Master” - will explore the role beyond simple facilitation of the Sprint Ceremonies. Attendees learn four different areas of focus for a balanced approach to the role.
Çevik Proje Yönetimi Metodolojileri ve Scrum'ın TemelleriOzan Ozcan
13.02.2019 tarihinde Atölye15 Talks etkinliğinde kullanılan sunumdur.
Proje Yönetimi Tarihçesi, Çevik proje yönetimi metodolojileri, Scrum tarihçesi, rolleri, toplantıları ve uygulama örnekleri yer almaktadir.
explains basic scrum jargon and details regarding scrum like duties of product owner,duties of scrum master,duties of development team,sprint planning,daily scrum,sprint overview,sprint retrospective
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
How leadership of employees via Objectives and Key Results (OKR) speeds up th...die.agilen GmbH
The major players in the industry - such as Google, LinkedIn, Zalando, Red Bull, Oracle & Co. - demonstrate it. In modern enterprises, a modern and contemporary framework is used for personnel management - OKR (Objectives & Key Results). Are goal management and "New Work" opposites? OKR combines
both! We explain the method and the framework in detail and show why it is so successful in times of digital transformation - even or especially at EDEKA.
Startup vs Corporate Products by Oracle's Director of ProductProduct School
What to expect and not to expect when you are working for a small company vs. a multi-billion dollar company as a Product Manager. All things considered, what will you learn and where will you have more fun doing what you like to do as a Product Manager.
Main Takeaways:
- Understanding how product functions in different organizations and leveraging that to take the next step
- Working within a product team
- Taking core product principals and making them your own
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
Objective
• Understand Agile software development
• Difference between Waterfall and Agile methodology
Agile Manifesto
Agile Benefits for Business
Agile Benefit for Developers
• Agile Umbrella
Scrum - Framework
Things we do in Scum
Scrum Team
User Stories
Prioritization - MoSSCoW
Sprint – Planning Meeting
Daily Scrum Meeting
Sprint Review Meeting
Sprint Retrospective
Scrum Values
• Tool to manage Agile Teams
Jira Software
Scrum is an iterative and incremental agile software development framework for managing product development. Diceus is following this methodology in various of projects, which give us and our clients invaluable advantage during development life cycle. The result of this approach is always stable and successful product.
You could find more information about Scrum methodology and Business Intelligence in our blog:
http://blog.diceus.com/
How to Build a Product Roadmap by eBay Director of ProductProduct School
Sudha Mahajan talked about how to build great roadmaps! Great roadmaps require right trade-offs, right prioritization, strong execution rigger and above all success metrics. A strong roadmap is your channel to success. There is no one size that fits all, but there are certain techniques that can help you get there.
Learn more about the most popular Agile framework - Scrum. This training should be paired with the pre-training learning materials in Trello. Learn more about the Scrum artifacts (product backlog, sprint backlog, etc.), Scrum roles (Scrum Master, Product Owner, and the team), and the Sprint.
What does a Scrum Master do all day if a Daily Scrum is only 15 minutes? This talk - “A Day in the Life of a Scrum Master” - will explore the role beyond simple facilitation of the Sprint Ceremonies. Attendees learn four different areas of focus for a balanced approach to the role.
Çevik Proje Yönetimi Metodolojileri ve Scrum'ın TemelleriOzan Ozcan
13.02.2019 tarihinde Atölye15 Talks etkinliğinde kullanılan sunumdur.
Proje Yönetimi Tarihçesi, Çevik proje yönetimi metodolojileri, Scrum tarihçesi, rolleri, toplantıları ve uygulama örnekleri yer almaktadir.
explains basic scrum jargon and details regarding scrum like duties of product owner,duties of scrum master,duties of development team,sprint planning,daily scrum,sprint overview,sprint retrospective
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
How leadership of employees via Objectives and Key Results (OKR) speeds up th...die.agilen GmbH
The major players in the industry - such as Google, LinkedIn, Zalando, Red Bull, Oracle & Co. - demonstrate it. In modern enterprises, a modern and contemporary framework is used for personnel management - OKR (Objectives & Key Results). Are goal management and "New Work" opposites? OKR combines
both! We explain the method and the framework in detail and show why it is so successful in times of digital transformation - even or especially at EDEKA.
Startup vs Corporate Products by Oracle's Director of ProductProduct School
What to expect and not to expect when you are working for a small company vs. a multi-billion dollar company as a Product Manager. All things considered, what will you learn and where will you have more fun doing what you like to do as a Product Manager.
Main Takeaways:
- Understanding how product functions in different organizations and leveraging that to take the next step
- Working within a product team
- Taking core product principals and making them your own
Product Management Course for all aspirants transitioning into the most in-demand role as a product manager.
Introduction to Product Management.
Foundations of Product Discovery.
The process of Product Definition.
Essentials of Product Delivery.
All the strategic concepts that will shape your attitude and mindset.
What is Product Success by Cayan Dir of Product EngineeringProduct School
In the presentation, Tcheilly Nunes, comes up with three takeaways that he believes are the key for a successful product:
-Having way fewer meetings
-Fostering healthy team debates
-Making product decisions everyone understands
How to Find Success in a Product Manager Role by GoGuardian PMProduct School
GoGuardian is an EdTech company in Los Angeles that scaled from an idea to a $100M company in just over three years with a great deal of ups and downs along the way.
Cody Rice, Product Manager at GoGuardian, talked about the ins and outs from a product perspective without having to make your own mistakes. This includes building an MVP, getting a product to the market, how to hire your product team, and what NOT to do as a Product Manager. But most importantly, when you have cost your company millions, feel like everything is on fire, and are scrambling to keep the plates spinning, how a simple mindset change can provide light years of growth and allow you to find success in your own career.
How to Design Your Own Career by Cylance Product ManagerProduct School
In this presentation, Matt Wilson, discusses how treating your career like a product to be managed can clarify your thinking on what is important (and what's not) in helping land that first Product Manager gig or move to your next role. Learn how basic Product Management techniques can be applied to personal career management. This presentation is punctuated by real examples from Matt's personal career journey from Engineer to Product Manager.
The Product Perspective on Problem Solving by former Visa PMProduct School
As an Engineer Sarika used to jump to the question - How ? How do I solve this problem ?
But as a Product Manager she had to change her perspective. Sarika added many more questions before coming to how. The general checklist she follows is :
-What is the problem?
-What is the severity of impact?
-What are our short term and long term options?
-Communication : Internal vs External?
Sachin Rekhi shares the 4 dimensions of product management (vision, strategy, design, execution), discusses where product managers fit in the R&D organization, and how product management roles differ across and within companies.
How to Make Your Resume Product Friendly by Ticketmaster PMProduct School
How to transform your resume to apply for a Product Management position?
Are you trying to break into Product Management and having a hard time getting called in for an interview? Thinking your resume may be affecting your chances? In this session, Haydee gave tips on how to transform your resume so that it highlights the experience and skills to get you in the door. This session is ideally suited for User Experience professionals, Business Analysts, or Developers seeking to transition into Product Management.
How to be a Digital Products Ninja by ServiceNow Sr. PMProduct School
Main takeaways:
- Learn how to be an expert product Ninja in the continuously changing digital world
- Learn about top 7 productivity hacks for Product Managers
- Best practices and framework for the product manager’s toolbox
Product Management 101: #1 How To Create Products Customer Love.Jean-Yves SIMON
An introduction to Product Management, for people involved in technology or software companies. Mainly aimed at evangelizing the role and responsibilities across an organization.
This is the #1 presentation out of a serie of 10 sessions.
Special thanks to Marty Cagan @ SVPG for the title :)
How to be a Digital Products Ninja by ServiceNow Sr. PMProduct School
Main takeaways:
- Learn how to be an expert product Ninja in the continuously changing digital world
- Learn about top 7 productivity hacks for Product Managers
- Best practices and framework for the product manager’s toolbox
What is B2B vs. B2C Product Management by Couchbase Senior PMProduct School
Ever wondered what the difference is between B2B and B2C product management? Enterprise Product Management has different challenges and rewards than consumer products and while you may find that consumer products are more exciting, working on an enterprise product is extremely fascinating as well. This presentation will talk you through the differences.
What Early Startup Life is Like as a PM by Zava Product OwnerProduct School
Main Takeaways:
- Get comfortable wearing many hats
- Everything is unknown/based on assumptions - question everything you, think, you know
- Re-think everything if/when you pivot
How Great PMs Can Come From Anywhere by ICX Media CPOProduct School
Main takeaways:
- 5 Different Personalities of Product Managers
- Product Managers Can Come from Many Different Functions
- Shared Traits of Successful Product Managers
How to Influence Using Data by Microsoft 365 Product ManagerProduct School
If you are a new PM and want to build trust with your team, or you find yourself fighting for technical approval and struggle with getting your work prioritized, you don’t want to miss this session.
The Butterfly Principle for Product Management by GameBench CEOProduct School
Startups have changed the way technology companies perceive product management. Experimentation and application of lean principles are no longer just for startups. Large enterprises want to cultivate a startup mindset and mimic such an environment.
So what’s the startup product mindset? How does obsession with a customer problem help startups succeed? And what makes them fail?
Sri shared his experiences and real examples around customer-centric and pragmatic product management that gives enterprises an edge over their competitors. He discussed the butterfly principle in product creation and how it helps create products customer love.
Similar to Moving from Business Analyst to Product Owner to Product Manager (20)
How to discover the right product to solve the right problemKent McDonald
Have you ever found yourself working as part of a large program with a lot of activity but not much progress? It could be rewriting a 20 year old system, customizing a COTS application, or building a data warehouse.
You may have been told that adopting agile approaches will help you deliver those types of efforts better, faster, and cheaper. You may have also found out that it’s not quite that simple. If you make your delivery process more efficient, you may just be delivering the wrong solution to the wrong problem faster.
Joint Kent McDonald to find out a practical and effective approach to discern if you’re solving the right problem,and discover the right product to address that problem. You’ll learn how to structure your next project to:
* Identify the problem you’re trying to solve
* Make sure the problem is worth solving
* Iteratively discover the right product to solve that problem.
Along the way you’ll learn about and practice a collection of simple techniques that you can use right away.
Learning Objectives:
1) How to use a problem statement to help your team understand the problem you’re trying to solve and determine if it’s worth solving
2) How to use decision filters and story maps to guide your efforts to discover the right product
3) How to use backlog refinement techniques to build a shared understanding of your product
How to Find the Real Need with Socratic QuestioningKent McDonald
A common piece of advice is that your team should discover the true need of your project. Unfortunately advice on how to make that happen isn’t as prevalent. In this session you’ll learn about a simple technique to get to the core of what your stakeholders need that has been around for over 2000 years – Socratic questioning.
Join Kent McDonald as he walks you through a technique aimed at uncovering the (not intentionally) hidden need that your stakeholders are trying to satisfy, without asking “why?” five times in a row. Kent describes the questions, why they work and in what context they work based on his experience with IT organizations and the Agile Alliance. You’ll then have a chance to consider how to use socratic question for a real life situation..
Come learn about this technique so you can use it back at the office to drive toward the right outcome.
Learning Objectives:
* Learn what socratic questioning is
* Learn how to identify your stakeholders needs using socratic questioning
* Determine when Socratic question is an appropriate technique to use
Ok, perhaps I should say that differently. The concept of a stakeholder is problematic.
Technically, a stakeholder is anyone who impacts or is impacted by an organization’s actions or products. That definition of a stakeholder isn’t very helpful if you’re trying to differentiate between customers, users, and those internal folks who have an interest in your product. To keep things straight, I apply the term stakeholders to that third group specifically. Stakeholders play a big part in internal products, so you can’t ignore your stakeholders and you can’t focus solely on them either.
Join Kent McDonald in this Ask Me Anything session focused on working with stakeholders. Kent has spent more years than he cares to admit working with all different types of stakeholders, and now he’d like to answer your questions and (hopefully) help you avoid some of the mistakes he’s made along the way.
So bring your questions about working with stakeholders and Kent will answer them. Anything he doesn’t get a chance to answer during the session he’ll follow up with answers after the session.
Learning Objectives:
Some questions we will most certainly address:
How to know if you’re dealing with a customer, a user, or stakeholder and why that’s important
How to identify the stakeholders you need to deal with and how you should deal with them
How to keep your stakeholders up to speed on what you’re up to.
How to build shared understanding with example mappingKent McDonald
One of the primary responsibilities of business analysts, product owners, and all other product people is to build and maintain a shared understanding of the outcome your team seeks to deliver. Conversations are an effective way to build that shared understanding.
You may find yourself wondering who should be included in those conversations, when do you have these conversations, what should you talk about, and how do you remember what you said?
Join Kent McDonald as he introduces example mapping, a technique that helps you structure your conversations and build a shared understanding.
You’ll learn how to determine the right people to include in your conversations, when the best time is to have those conversations, how to structure those conversations, and how to remember what you said.
How to build shared understanding with example mappingKent McDonald
One of the primary responsibilities of business analysts, product owners, and all other product people is to build and maintain a shared understanding of the outcome your team seeks to deliver. Conversations are an effective way to build that shared understanding.
You may find yourself wondering who should be included in those conversations, when do you have these conversations, what should you talk about, and how do you remember what you said?
Join Kent McDonald as he introduces example mapping, a technique that helps you structure your conversations and build a shared understanding.
You’ll learn how to determine the right people to include in your conversations, when the best time is to have those conversations, how to structure those conversations, and how to remember what you said.
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed at all, depends a great deal on context. As teams discover this, it leads to some common questions:
What do Product Owners Really Do?
Do we even need Product Owners?
Join Kent to examine the Product Owner role and attempt to answer the above questions. He’ll share his experiences and give you a chance to share your perspectives with each other.
By the end of the session, you'll have more insight into the Product Owner role and how it applies (or not) to your situation. This includes an understanding of common organizational models for product owners (including what part of the organization they fit in), how to determine appropriate product ownership responsibilities for your situation, and whether you need Product Owners to have successful product ownership.
How to Find the Real Need with Socratic QuestioningKent McDonald
A common piece of advice is that your team should discover the true need of your project. Unfortunately advice on how to make that happen isn't as prevalent. In this session you'll have a chance to practice a simple technique to get to the core of what your stakeholders need that has been around for over 2000 years - Socratic questioning.
Kent McDonald and Heather Mylan-Mains walk you through a technique aimed at uncovering the (not intentionally) hidden need that your stakeholders are trying to satisfy, without asking "why?" five times in a row. Kent & Heather describes the questions, why they work and in what context they work based on their experience with IT organizations. You'll then have a chance to practice them out to find out about a real project.
The line of questioning was inspired by Brennan Dunn who uses them to understand the true needs of his web development consultants.
Come learn about and practice this technique so you can use it back at the office to drive toward the right outcome.
Agile Leadership: Accelerating Business Agility - ContextKent McDonald
The "one size fits all" approach to Project Leadership is inherently flawed. Practitioners have found that the two primary attributes of uncertainty and complexity of a project provide guidance to effective project leadership and governance. Complexity includes project composition such as team size and criticality, while uncertainty includes both market and technical uncertainty. The approach and leadership style required for a simple, stable project is quite different than what is required for highly uncertain, highly complex projects. This session demonstrates how to use the Context Leadership Model to determine the appropriate approach and leadership style for a project based on its uncertainty and complexity.
Key Learning Points
How to assess the complexity and uncertainty characteristics of a project
How to tailor the project approach based on those characteristics
How to determine the appropriate leadership style for a project based on its characteristics
How to find the real need with socratic questioningKent McDonald
A common piece of advice is that your team should discover the true need of your project. Unfortunately advice on how to make that happen isn't as prevalent. In this session you'll have a chance to practice a simple technique to get to the core of what your stakeholders need that has been around for over 2000 years - Socratic questioning.
Join Kent McDonald as he walks you through a technique aimed at uncovering the (not intentionally) hidden need that your stakeholders are trying to satisfy, without asking "why?" five times in a row. Kent describes the questions, why they work and in what context they work based on his experience with IT organizations and the Agile Alliance. You'll then have a chance to practice them out to find out about a real project.
The line of questioning was inspired by Brennan Dunn who uses them to understand the true needs of his web development consultants.
Come learn about and practice this technique so you can use it back at the office to drive toward the right outcome.
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed at all, depends a great deal on context. As teams discover this, it leads to some common questions:
What do Product Owners Really Do?
Do we even need Product Owners?
Join Kent to examine the Product Owner role and attempt to answer the above questions. He’ll share his experiences and give you a chance to share your perspectives with each other.
By the end of the session, you'll have more insight into the Product Owner role and how it applies (or not) to your situation. This includes an understanding of common organizational models for product owners (including what part of the organization they fit in), how to determine appropriate product ownership responsibilities for your situation, and whether you need Product Owners to have successful product ownership.
Tis better to be effective than efficientKent McDonald
Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.
It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.
Effectiveness may just be the better target.
Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:
Build a shared understanding of the problem you are trying to solve
Establish clear guard rails for distributed decision making
Measure progress based on outcome, not output
Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.
You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective. Come to this session to learn how.
Do you work at an organization that is "scaling" agile or thinks they need to do "agile at scale"?
Do you find yourself asking these questions:
- What does scaling agile really mean, and is it necessary that we scale?
- If scaling means working with a large team, how do we make sure everyone is moving in the same direction?
- How do we deal with the complications that come with scaling, such as the dependencies that are inherently created?
Join Kent McDonald as he suggests answers to these questions in the form of 3D’s:
- Do "scaling" only when necessary
- Decision making in a complicated environment
- Dependencies and how to deal with them
As we examine these topics, Kent introduces simple, yet powerful techniques your teams can use to be more effective in an environment where scaling seems to be the right answer. You’ll walk away with ideas on how to apply these techniques in your own situation.
Learning Outcomes:
- Use the Context Leadership Model and the Cynefin model to determine if scaling is the right answer
- Encourage informed decision making through Purpose Based Alignment and decision filters
- Minimize dependencies through collaborative planning & consistent communication
What do Scrum Masters Really Do? And do we need them?Kent McDonald
The Scrum Master role is a foundational concept of Scrum, yet like everything else, the role and it’s value should not be fixed. As with everything else related to agile, the nature of the Scrum Master role, and whether it is needed or all, depends a great deal on context. As teams discover this, it leads to some common questions:
* What do Scrum Masters Really Do?
* Do we even need Scrum Masters?
Join Jodi and Kent as we examine the Scrum Master role and attempt to answer the above questions. We’ll share our experiences and give you a chance to share your perspectives with each other. By the end of the session, you'll have more insight into the Scrum Master role and how it applies (or not) to your situation.
After all, the only consistent answer to the above questions is “it depends”.
Have you ever found yourself in a conversation with stakeholders, development team, or both that was going no where? Do you find that the written word never quite conveys what you are trying to say? Are you a believer in the saying “a picture is worth a 1,000 words?” Are you always looking for the closest whiteboard and marker?
You may want to try collaborative modeling.
Collaborative modeling refers to the use of well-known requirements modeling techniques in a collaborative fashion to build and maintain a shared understanding of your problem space and potential solution(s).
Join Kent to explore how to use requirements models as collaborative elicitation and analysis techniques with your delivery team and stakeholders. We won’t necessarily cover how to do create every specific type of model, but we will talk about when specific techniques are the most helpful, and how to use them in a collaborative fashion.
Learning Objectives:
- When specific modeling techniques may be the most helpful
- How to model collaboratively
- Why collaborative modeling is effective
Analysis With an Agile Mindset WorkshopKent McDonald
Analysis is often portrayed as eliciting and documenting requirements, frequently in terms that sound a lot like asking people what they want and writing it down. Analysis is about understanding your stakeholders and their needs, identifying the best solution for satisfying those needs in your particular context, and then building a shared understanding of that solution. Requirements play a part in that work, especially around describing the need, but they are certainly not the end product.
In this session, Kent McDonald will guide you through an approach to analysis in an agile manner. You’ll see examples of techniques that will help you understand stakeholders, context, and needs and then determine and describe possible solutions. You’ll then get an opportunity to try those techniques out on a case study. Along the way you’ll find out how to use analysis to determine if you are doing the right thing and how to determine how much analysis is just enough.
Key takeaways:
- Identify and understand potential users with user modeling.
- Determine the appropriate design approach for your project using the Purpose Based Alignment Model.
- Use decision filters to clearly state the desired outcome of your project and provide team with information for decision making.
- Identify and describe backlog items in more detail using collaborative modeling.
Elicitation and requirements analysis are some business analysis skills that are extremely helpful in an agile setting especially for team members responsible for product ownership. Equally helpful, if not more so, are the skills that teams use to interact with stakeholders, make decisions, and react to actual situations as they arise. The best way to understand the relevance of these skills is to share stories of successful, and perhaps not so successful interactions on real projects and discuss what the team learned. Join Kent as he shares stories from his experiences as Submission System Product Owner and relates the things he learned to useful skills for all business analysts. You’ll get a chance to tell Kent where he went wrong and also consider how to apply the lessons learned in your own setting. Along the way you’ll hear about some techniques for addressing common project situations that work well as long as you get the nuances right.
You have been tapped for an exciting new project. A member of the executive team recognizes that the company needs to transform to meet the evolving needs of your dynamic marketplace. They know that Agile will be part of that transformation, they tap you to lead the effort, and now they think their work is done . While that is exciting and an honor for you, you still need the active engagement of the senior leadership team to create a culture where Agile practices can flourish. The support from the top is critical to drive the type of innovation and flexibility that will be required to successfully implement any new idea – but especially one as (positively) disruptive as Agile.
This session describes how senior leaders need to act differently in an enterprise transitioning to agile, and some helpful patterns individual contributors can use to leverage politics in a positive manner to lead up through influence and help senior leaders make the transition. These patterns are based on Heather and Kent’s experiences at a variety of organizations driving or helping to drive changes including, but not limited to adopting agile approaches. Along the way, we’ll give you a chance to share your thoughts and experiences using politics in a positive (or perhaps not so positive) way to help an enterprise transition to agile.
Anyone Can Write User Stories. It's the (Shared) Understanding That's ImportantKent McDonald
“Who should write user stories?”
“How can I write better user stories?”
When should we write user stories?”
All questions frequently asked. And all questions entirely missing the point.
Just as the *holding* is the most important part of the rental car reservation, the *shared understanding* is the most important part of the user story.
Join Kent to learn how user stories help you build shared understanding of the right solution with your team. Along the way, learn some techniques to address common issues that stand in the way of getting everyone telling the same story.
Learning Objectives:
* Start with value, then identify stories
* One way to stop solutioning
* Dealing with dependencies (that may not be there) within your backlog
* Ways to split user stories into a more manageable size
* Mapping your way to acceptance criteria
Want to move your career forward? Looking to build your leadership skills while helping others learn, grow, and improve their skills? Seeking someone who can guide you in achieving these goals?
You can accomplish this through a mentoring partnership. Learn more about the PMISSC Mentoring Program, where you’ll discover the incredible benefits of becoming a mentor or mentee. This program is designed to foster professional growth, enhance skills, and build a strong network within the project management community. Whether you're looking to share your expertise or seeking guidance to advance your career, the PMI Mentoring Program offers valuable opportunities for personal and professional development.
Watch this to learn:
* Overview of the PMISSC Mentoring Program: Mission, vision, and objectives.
* Benefits for Volunteer Mentors: Professional development, networking, personal satisfaction, and recognition.
* Advantages for Mentees: Career advancement, skill development, networking, and confidence building.
* Program Structure and Expectations: Mentor-mentee matching process, program phases, and time commitment.
* Success Stories and Testimonials: Inspiring examples from past participants.
* How to Get Involved: Steps to participate and resources available for support throughout the program.
Learn how you can make a difference in the project management community and take the next step in your professional journey.
About Hector Del Castillo
Hector is VP of Professional Development at the PMI Silver Spring Chapter, and CEO of Bold PM. He's a mid-market growth product executive and changemaker. He works with mid-market product-driven software executives to solve their biggest growth problems. He scales product growth, optimizes ops and builds loyal customers. He has reduced customer churn 33%, and boosted sales 47% for clients. He makes a significant impact by building and launching world-changing AI-powered products. If you're looking for an engaging and inspiring speaker to spark creativity and innovation within your organization, set up an appointment to discuss your specific needs and identify a suitable topic to inspire your audience at your next corporate conference, symposium, executive summit, or planning retreat.
About PMI Silver Spring Chapter
We are a branch of the Project Management Institute. We offer a platform for project management professionals in Silver Spring, MD, and the DC/Baltimore metro area. Monthly meetings facilitate networking, knowledge sharing, and professional development. For event details, visit pmissc.org.
The Impact of Artificial Intelligence on Modern Society.pdfssuser3e63fc
Just a game Assignment 3
1. What has made Louis Vuitton's business model successful in the Japanese luxury market?
2. What are the opportunities and challenges for Louis Vuitton in Japan?
3. What are the specifics of the Japanese fashion luxury market?
4. How did Louis Vuitton enter into the Japanese market originally? What were the other entry strategies it adopted later to strengthen its presence?
5. Will Louis Vuitton have any new challenges arise due to the global financial crisis? How does it overcome the new challenges?Assignment 3
1. What has made Louis Vuitton's business model successful in the Japanese luxury market?
2. What are the opportunities and challenges for Louis Vuitton in Japan?
3. What are the specifics of the Japanese fashion luxury market?
4. How did Louis Vuitton enter into the Japanese market originally? What were the other entry strategies it adopted later to strengthen its presence?
5. Will Louis Vuitton have any new challenges arise due to the global financial crisis? How does it overcome the new challenges?Assignment 3
1. What has made Louis Vuitton's business model successful in the Japanese luxury market?
2. What are the opportunities and challenges for Louis Vuitton in Japan?
3. What are the specifics of the Japanese fashion luxury market?
4. How did Louis Vuitton enter into the Japanese market originally? What were the other entry strategies it adopted later to strengthen its presence?
5. Will Louis Vuitton have any new challenges arise due to the global financial crisis? How does it overcome the new challenges?
Operating system. short answes and Interview questions .pdf
Moving from Business Analyst to Product Owner to Product Manager
1. Moving from Business Analyst to
Product Owner to Product Manager
Kent J. McDonald
kentjmcdonald@gmail.com
https://insideproduct.co/bbc-2023
2. A little bit about me
Industrial
engineer by
training
Recovering agile
coach
Started Business
Analysis to
learn IT
Unemployable
Write to learn
and earn
Proj Mgr / BA
rotation
Content
Creator/ Trainer
Practice to stay
current
Product
manager for
Enabling
Products
3. A little bit about you
Stand up if you are a…
Business
Analyst
Product
Owner Product
Manager
13. Why move into product?
Lies, Damn Lies, and Statistics
Job Openings (April 27,2023 USA) Salaries (April 27, 2023 USA per Glassdoor)
Role LinkedIn Indeed
Product
Manager
140,241 13,924
Product
Owner
81,343 9,369
Business
Analyst
40,243 12,806
Role Min Average Max
Product
Manager
61,000 102,223 170,000
Product
Owner
57,000 90,409 143,000
Business
Analyst
51,000 76,498 115,000
More
Jobs
More
Money
14. Why become a product owner?
Prefer working
with devs &
Designers to
build solution
Your org has
gone through
agile
transformation
PO = BA +
Decisions
15. Why become a product manager?
Want to work
with product
team in both
areas
Your org is
going through
product
transformation
PM = BA +
Decisions +
Experiments +
user research
16. Product Transformation
Project Orientation Product Orientation
How much will this cost? Budgeting How much are we
willing to spend?
Fixed Duration Time Frame Entire Product LifeCycle
Deliver an assigned solution Defn of Scope Asked to Solve a problem
Output, on Time, in Budget Success Accomplish Outcome
Temporary, Split Focus,
Pulled from Resource Pools
Team Makeup Stable, dedicated,
All Needed Skills
Build only Team Owns Build and Run
Expense IT Org Investment
20. Teams
that own
Systems in
your org
teams that
own your
orgs
Products
B2C or
B2B SaaS
Products
Same type
of system,
different
org
Pick up strategy
skills
Figure out how
to measure
outcomes
Find the teams
already “doing”
product
Practice
discovery with
your users
Figure out how
your work
impacts
customers
21. Teams
that own
Systems in
your org
teams that
own your
orgs
Products
B2C or
B2B SaaS
Products
Same type
of system,
different
org
Build a network
through events
like this
Find companies
in an industry
you’re familiar
with
Describe your BA
work in product
terms
Practice user
research on
Org’s customers
Learn what you
can about
target Org’s
strategies
23. Teams
that own
Systems in
your org
teams that
own your
orgs
Products
B2C or
B2B SaaS
Products
Same type
of system,
different
org
Work on
customer facing
systems as an
interim step
Be very familiar
with your org’s
products
Practice
discovery on your
org’s customers
Familiarize
yourself with
Market and
Competitors
Network with
Product
Managers in
your org
24. Teams
that own
Systems in
your org
teams that
own your
orgs
Products
B2C or
B2B SaaS
Products
Same type
of system,
different
org
Consider B2B
Enterprise
products
Create your own
product
Find companies
in an industry
you’re familiar
with
TRY.
THE.
PRODUCT.
Describe your BA
experience in
product terms
26. Don’t worry about title, focus on skills
Title: Delivery Lead
What I Did: Map current state, design database, model
processes, IDentify Business RUles, Coach team
27. Explain how BA experience applies to
Product Management
Focus on accomplishments instead of activity
How did you help customers solve problems, and meet
business objectives
28. Do Discovery (and Analysis) in increments
Refinement Board
Delivery Board