Kent McDonald explains how Business Value is a conversation, not a number, at the Agile Testing & BDD eXchange in New York (Oct 1sr 2012). Find this and other presentations at this conference her:
http://skillsmatter.com/event/agile-testing/agile-testing-and-bdd-exchange-nyc/wd-23
IT managers often talk about the technology in far more technical terms than business people can understand (or actually care about!).
If stronger communication and integration is to take place between the IT and other internal business units, then IT needs to learn how to talk and listen very differently.
Dr. Anderson provides guidance about how to be a better business communicator focusing on how to create and deliver presentations that contain detailed technical information in a way that is engaging to a non-IT audience and allows you to better connect with business people.
For more information on Dr. Jim Anderson and his company, Blue Elephant Consulting, find out more on the web at http://www.BlueElephantConsulting.com
IT managers often talk about the technology in far more technical terms than business people can understand (or actually care about!).
If stronger communication and integration is to take place between the IT and other internal business units, then IT needs to learn how to talk and listen very differently.
Dr. Anderson provides guidance about how to be a better business communicator focusing on how to create and deliver presentations that contain detailed technical information in a way that is engaging to a non-IT audience and allows you to better connect with business people.
For more information on Dr. Jim Anderson and his company, Blue Elephant Consulting, find out more on the web at http://www.BlueElephantConsulting.com
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
Estimating in Software Development: No Silver Bullets AllowedKent McDonald
What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you’ll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work—analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations—guesstimating, break it down and add it up, and planning poker. Kent has found that these “lite” estimation techniques are almost always just as informative as the ones you just spent six weeks formulating.
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.
Some teams think they can be agile by using a defined process or set of practices as defined by one of the agile approaches. This is just “doing Agile.” Other teams are agile in name only – the team says it’s “doing Agile” but ends up using the same old practices and achieving the same results. Teams adopt agile for a variety of reasons, but it’s not the process or set of practices they select that produces the results they seek. Teams are most successful when they adopt a particular mindset in order to “be agile”. Join Kent McDonald as he describes this mindset through 7 key ideas based on how people and organizations work best. We’ll discuss some specific techniques you can use to adopt the mindset on your project, how the project manager role changes along with the mindset, and how to help your team move from “doing Agile” to actually “being agile”.
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”.
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
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.
Decision Making Techniques for Not for ProfitsKent McDonald
Agile approaches emphasize delivering business value to stakeholders. The concept of business value is a difficult concept to get your arms around, doubly so if you are working in a Not for Profit.
One way to address the problem is to see the idea of business value for what it is – an aid for making decisions. In this talk Kent McDonald describes three simple techniques that you can use to make decisions in your Not For Profit.
Kent describes how to apply the idea of business value to not for profits and shows how you can use three techniques – Real Options, Decision Filters, and Purpose Based Alignment to make decisions in any kind of organization, even Not for Profits.
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
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.
Analysis In Agile: It's More than Just User StoriesKent McDonald
A common question asked by teams adopting agile is "what does business analysis look like in agile?" The common answer is "writing user stories".
WRONG!
Okay, maybe not wrong, but certainly not the whole story (pardon the pun). Business analysis in agile is concerned with understanding the problem and possible solutions in order to ensure the team is building the right thing. User stories can be helpful, but are certainly not sufficient for doing that.
In this session, Kent McDonald describes how you can perform just enough business analysis to discover the right things to build. This includes how to really use value to decide what to build first, why process flows, data models, and mockups are still extremely helpful, and why the function of user stories is more important than their form.
Along the way, Kent shares examples from a system replacement project he is working on and suggests ways you can apply these techniques to your own projects.
Is It Worth It? Using A Business Value Model To Guide DecisionsKent McDonald
One trait of an effective business analyst is the ability to ask the right questions. One “right” question that applies to just about every projects can sometimes be difficult to ask, let alone answer: “Is it worth it?” This question is difficult to answer, because the answer will change as you proceed through the project and gain more knowledge about the purpose, considerations, costs, and benefits involved in a project.
In this session, we’ll explore a tool you can use to help organize the necessary information to answer the “is it worth it?” question on a regular basis. This interactive session will demonstrate how you can create a value model to make an initial decision about whether to pursue a project, and then utilize that model as your knowledge grows throughout the project to revisit the question and confirm whether the project is on the right course, or if changes need to be made.
Topics discussed during the session include:
Structuring your value model to make decisions about whether to do a project
How to deal with non-financial benefits in your Cost/Benefit discussion
Where measures such as NPV, ROI, TCO, IRR fit into the Cost/Benefit discussion.
The impact of timing of implementation on the Cost/Benefit discussion.
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.
Agile India 2016 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Adoption, Scaling Agile, Offshore Agile and Distributed Agile. 14 - 21 March 2016 at Chancery Pavilion, Bangalore. More details: http://2016.agileindia.org
Understanding Roles on an Agile ProjectKent McDonald
The ideal agile team is a self organizing, dedicated, cross functional group that has all the skills necessary to deliver a solution that solves their customer’s problem. As a result, the list of roles on an agile team is fairly short generally consisting of roles such as Scrum Master, Product Owner, and the Team. Given all that, many project managers wonder where they fit in. They may act as the Product Owner if they have the skill set and decision making authority to determine what the product should contain. They may become the Scrum Master if they are able to practice servant leadership and act as a coach and facilitator. They may become part of the team and help develop or test. They may focus on coordinating the efforts of multiple agile teams to support the broader goals of a large program. They may not be a good fit for an agile environment at all. Join Kent McDonald as he describes the Product Owner and Scrum Master roles in an agile environment and discusses the various ways that project managers can assess their skill sets and project characteristics to determine where they fit into the picture.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
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 Develop Value Propositions, for CIOsWalter Adamson
CIO Business Innovation Series. Paul DiModica, author of the book “Sell Technology: Technology Sales Is a Premeditated Sport”, talks about technology salesmen:
Q: What are the top mistakes people make when selling technology? Well, first of all, most of them come to sell instead of listen. They're not prepared, and they tend to shoot from the hip. Secondly, they don't know what they're selling.
Q: They don't understand their product? No, it's deeper than that. They don't understand the value of what they're selling and, consequently, can't explain its value. And thirdly, they sell technology instead of a solution.
If your IT leadership team is having the same problems, then you are not alone.
Learn how to solve the problem.
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
Estimating in Software Development: No Silver Bullets AllowedKent McDonald
What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you’ll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work—analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations—guesstimating, break it down and add it up, and planning poker. Kent has found that these “lite” estimation techniques are almost always just as informative as the ones you just spent six weeks formulating.
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.
Some teams think they can be agile by using a defined process or set of practices as defined by one of the agile approaches. This is just “doing Agile.” Other teams are agile in name only – the team says it’s “doing Agile” but ends up using the same old practices and achieving the same results. Teams adopt agile for a variety of reasons, but it’s not the process or set of practices they select that produces the results they seek. Teams are most successful when they adopt a particular mindset in order to “be agile”. Join Kent McDonald as he describes this mindset through 7 key ideas based on how people and organizations work best. We’ll discuss some specific techniques you can use to adopt the mindset on your project, how the project manager role changes along with the mindset, and how to help your team move from “doing Agile” to actually “being agile”.
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”.
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
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.
Decision Making Techniques for Not for ProfitsKent McDonald
Agile approaches emphasize delivering business value to stakeholders. The concept of business value is a difficult concept to get your arms around, doubly so if you are working in a Not for Profit.
One way to address the problem is to see the idea of business value for what it is – an aid for making decisions. In this talk Kent McDonald describes three simple techniques that you can use to make decisions in your Not For Profit.
Kent describes how to apply the idea of business value to not for profits and shows how you can use three techniques – Real Options, Decision Filters, and Purpose Based Alignment to make decisions in any kind of organization, even Not for Profits.
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
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.
Analysis In Agile: It's More than Just User StoriesKent McDonald
A common question asked by teams adopting agile is "what does business analysis look like in agile?" The common answer is "writing user stories".
WRONG!
Okay, maybe not wrong, but certainly not the whole story (pardon the pun). Business analysis in agile is concerned with understanding the problem and possible solutions in order to ensure the team is building the right thing. User stories can be helpful, but are certainly not sufficient for doing that.
In this session, Kent McDonald describes how you can perform just enough business analysis to discover the right things to build. This includes how to really use value to decide what to build first, why process flows, data models, and mockups are still extremely helpful, and why the function of user stories is more important than their form.
Along the way, Kent shares examples from a system replacement project he is working on and suggests ways you can apply these techniques to your own projects.
Is It Worth It? Using A Business Value Model To Guide DecisionsKent McDonald
One trait of an effective business analyst is the ability to ask the right questions. One “right” question that applies to just about every projects can sometimes be difficult to ask, let alone answer: “Is it worth it?” This question is difficult to answer, because the answer will change as you proceed through the project and gain more knowledge about the purpose, considerations, costs, and benefits involved in a project.
In this session, we’ll explore a tool you can use to help organize the necessary information to answer the “is it worth it?” question on a regular basis. This interactive session will demonstrate how you can create a value model to make an initial decision about whether to pursue a project, and then utilize that model as your knowledge grows throughout the project to revisit the question and confirm whether the project is on the right course, or if changes need to be made.
Topics discussed during the session include:
Structuring your value model to make decisions about whether to do a project
How to deal with non-financial benefits in your Cost/Benefit discussion
Where measures such as NPV, ROI, TCO, IRR fit into the Cost/Benefit discussion.
The impact of timing of implementation on the Cost/Benefit discussion.
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.
Agile India 2016 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Adoption, Scaling Agile, Offshore Agile and Distributed Agile. 14 - 21 March 2016 at Chancery Pavilion, Bangalore. More details: http://2016.agileindia.org
Understanding Roles on an Agile ProjectKent McDonald
The ideal agile team is a self organizing, dedicated, cross functional group that has all the skills necessary to deliver a solution that solves their customer’s problem. As a result, the list of roles on an agile team is fairly short generally consisting of roles such as Scrum Master, Product Owner, and the Team. Given all that, many project managers wonder where they fit in. They may act as the Product Owner if they have the skill set and decision making authority to determine what the product should contain. They may become the Scrum Master if they are able to practice servant leadership and act as a coach and facilitator. They may become part of the team and help develop or test. They may focus on coordinating the efforts of multiple agile teams to support the broader goals of a large program. They may not be a good fit for an agile environment at all. Join Kent McDonald as he describes the Product Owner and Scrum Master roles in an agile environment and discusses the various ways that project managers can assess their skill sets and project characteristics to determine where they fit into the picture.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
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 Develop Value Propositions, for CIOsWalter Adamson
CIO Business Innovation Series. Paul DiModica, author of the book “Sell Technology: Technology Sales Is a Premeditated Sport”, talks about technology salesmen:
Q: What are the top mistakes people make when selling technology? Well, first of all, most of them come to sell instead of listen. They're not prepared, and they tend to shoot from the hip. Secondly, they don't know what they're selling.
Q: They don't understand their product? No, it's deeper than that. They don't understand the value of what they're selling and, consequently, can't explain its value. And thirdly, they sell technology instead of a solution.
If your IT leadership team is having the same problems, then you are not alone.
Learn how to solve the problem.
3C's for Success: Create Confirm ConvinceCarol Dekkers
If you're finding that your great ideas fall on deaf (executive) ears - this presentation is for you! While originally developed and delivered for technical audiences (software sizing and estimation) - the concepts apply equally well in any industry. Instead of presenting/pitching/selling your concepts based on how your peers would want to hear them, we need to reframe them in executive terms - by using a 3 step process: Create, Confirm, Convince.
This workshop was created to provide a framework for thinking about and measuring marketing investment.
For more marketing advice, contact info@hawkpartners.com
5 Employee Relations Metrics you Should be Tracking & WhyDovetail Software
If tracked correctly, ER metrics can help determine the root cause of workforce trends in your organization. In this webinar, human capital strategy consultant and 20-year HR veteran Cathy Missildine-Martin will reveal five critical ER metrics you should be tracking and why.
Join us to learn:
* Why ER metrics are just as important to HR analytics as performance metrics
* How to use ER metrics to drive corporate policy change
* What ER metrics you should be tracking and what they reveal
* How to use technology to track, measure and report on ER metrics
This must-attend webinar will help ensure that you’re including the metrics necessary to paint a full picture of what’s going on in your organization’s workforce and have the insight you need to build an effective human capital strategy.
Understanding the Economic Value of Design v1Chris Finlay
Design has long struggled to justify its value as a business activity, and while it has gained ground it is still losing too often. Designers know it is the primary source of innovation, problem solving, and is one of the few truly sustainable competitive advantages.
What designers don't realize is that most business activities are either belief or superstition, rather than based on a reliable return on investment (ROI) calculation. Business people and designers lack a shared understanding of how design creates value, and so they use their specialized language to defend their position, and ultimately reduce the competitiveness of the business.
This is a work in progress on that issue, by Chris Finlay and Jason Gaikowski, focused on creating a critical chain of logic to help both business people and designers understand how to create value together.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Business valueiIs a conversation_kent-mcdonald_#bddxny
1. Business Value is a Conversation,
Not A Number
Kent J. McDonald
@beyondreqs
2. Agenda
What is business value?
Conversations that consider value
Did we deliver value?
3. The Prime Directive:
Deliver Business Value!
*The organizers
wish to apologize
for any gratuitous
trekkie references
that may appear
in this
presentation.
4. What is business value?
I’ll know it
when I see
it
Justice Potter Stewart, concurring opinion in Jacobellis v. Ohio 378 U.S. 184 (1964), regarding
possible obscenity in The Lovers.
18. How much should we build?
Always
Often or
7% Always used
Often 20%
Never 13%
45%
Sometimes
16%
Rarely
19%
Rarely or
Never used64%
Standish Group Study, Reported by CEO Jim Johnson, XP2002
29. I(a)
Taking it a step further…
I(t)
I(d)
Development
Example
In Scope? Model
Test
Test
The Missing Link!
I(tp)
30. Feature Injection
Business Analysis
feeding Examples into a
Development Process
(especially Agile)
Hunt the Value
“Inject” only relevant
features
Communicate with
examples
Devised by Chris Matts
34. Purpose Based Alignment Model
Do we take this Innovate,
on? Create
Achieve and
Minimize/ maintain parity,
Eliminate Mimic,
Simplify
35. Decision Filters
Simple rules to guide
decision making
Disperse throughout
the organization
Used for (among others)
Strategy alignment
Scoping
Design approach
36. “To be the low cost airline.”
- Southwest Airlines
37. “Will this help us be
the low cost airline?”
- Southwest Airlines
38. Purpose and Decision Filters
To be the
low cost
airline
Will this help us be
the low cost airline?
47. Sample Objectives
By Dec 2012 increase By Dec 2012 reduce paper
inventory turns from 5/year apps from 1,000/month to
to 10/year 500/month
48. Measuring Your Objectives
Objective 1 Objective 2
Measure Inventory Turns Paper Apps
Definition The number of times Number of apps received
inventory is sold in a year via mail or fax
Data Source Inventory Tracking System
What to Measure Cost of Goods Sold/ Average Count of applications
Inventory received via mail/fax
Frequency of Measure Yearly Monthly
Sample Size N/A N/A
Who will collect data Inventory Accounting Analyst Data entry specialists
How will data be collected Report created by Inventory Count paper applications
Tracking Systems when entered
Baseline 5 1000
Target 10 500
49. If you remember nothing else…
Business value is a
conversation to help us
decide:
Is it worth it?
How much should we
build?
How unique should it
be?
Use business objectives to
tell if you delivered value