This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
In Part 1 and 2 of this series, I wrote about how an agile approach might offer strategic benefits. And because an agile approach changes your culture, I said the agile approach was part of your strategy. So let's ask this question: Can any tool—agile or otherwise—offer you a strategic advantage? (I
The managers don't believe the teams need product owners, so the teams don't have POs. Those outcomes can help teams decide which agile approach(es) to start with and adapt. Let's start with who wants the teams to use an agile approach. Who Wants the Teams to Use an Agile Approach? They're having trouble with Scrum.
I have a new book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. I wrote it because I'm concerned about what I see in too many supposedly agile teams: Crazy-long backlogs and roadmaps. See Manage Unplanned Feedback Loops to Reduce Risks and Create Successful Products.)
Strategy and Product Feedback Loops Many of my middle-management and senior leadership clients want certainty about future work. But most of my business focuses on coaching, workshops, or consulting. Does that sound like an agile team to you? However, managers don't create features as agile teams do. I plan to replan.
I finished all the video editing for the writing workshop. Because there's more work to finishing the workshop, I'm sure I will not finish the workshop today. I don't have just one product for my business. And I'm not a team working on just one feature set or a product. But I can get ready to finish. What happened?
We talk a lot about empowered or self-organizing teams in the agile community. When Mark Kilby and I wrote From Chaos to Successful Distributed Agile Teams , we said the easiest way to create a system that worked for the team was for the team to create its own board. Agile Approaches Require Management Cultural Change.
I finished one week of the videos for the writing workshop. Finish another week of videos for the writing workshop because I want to announce it “soon.” And the writing workshop will make more money sooner than the book will. My cycle times for my various work: About an hour to complete the videos for workshop week.
For example, if your goal is to increase sales, your L&D programs might focus on enhancing sales techniques, product knowledge, or customer relationship management skills. Productivity metrics: Assess changes in output per employee or team efficiency. Output per employee: Track changes in individual or team productivity levels.
If you took an agileworkshop sometime in the past 15 years, you probably played the “ ball game.” Especially since they've probably suffered through way too many “agile” workshops with more and more games. We now have a team environment that can use agile principles, but we're not quite done.
The online workshop videos are complete. I also know my cycle times to develop workshops and video them. All this collaboration and learning together means the team shares its product development. Have a workshop to decide. You're workshopping.) If you're a product leader, you need a product value team.
Product owners have many challenges: They need to keep at least two thoughts about the product: what it needs to be in the near future, and what the organization wants it to be in the (distant) future. But the biggest problem I see is this: Effective product owners belong to at least two teams and maybe more. Strategic work.)
Now that agile teams stay together, we can change the kickoff to more project-specific work. I wrote an article several years ago, Keys to Chartering an Agile Project. In Create Your Successful Agile Project , I suggested a reframe for the charter. Many new-to-agile-thinking teams want everything defined upfront.
At the Influential Agile Leader workshop earlier this year, I led a session about scaling and how you might think about it. I asked if any of the teams succeeded at using an agile approach at the team level. I explained how in Agile and Lean Program Management.). ” Agile Scaling is the Answer to Whose Problems?
By embedding learning into the organization’s fabric, companies can remain competitive and agile in the face of change. Enhancing Employee Skills : Through targeted training programs, employees can develop new competencies that significantly enhance their performance and productivity.
Originating from agile software development, the sprint has entered the business mainstream as an increasingly popular means to accelerate business model, product, or service innovation. They allow a company to be more agile and to more effectively adapt to digital disruption. Can you run fast and go deep at the same time?
Strategy and Product Feedback Loops About 20 years ago, I taught a project management workshop to IT people. Their products and services did not ship outside the building—their products and services enabled the organization to make money. Adam, a product leader, has changed his meetings and workshops.
Instead of incurring the time and cost when you bring everyone together, consider the Product Value Team. (In In past writing and presentations, I’ve called this the Product Owner Value Team. I am trying to change my term to the Product Value Team.). The product value team is a different kind of a team.
I suggested ways to think about more agile budgeting in part 1. I evaluate the plan—my products, services, and clients—on a regular basis. I can also predict how long it takes me to create or customize an in-person workshop. I have an upper bound for online workshops. I didn't tell you why.
” These people claim there is no need for either role in an effective team, especially an agile team because the team can manage its own deliverables. While some agile teams can manage their own deliverables, that's not the only role for a project or program manager. Clarify the Product and Team Objectives. The outcomes).
The Forum participants will have an opportunity to learn from inspirational project management leaders as well as attend masterclasses revealing the aspects of delivering sustainable projects, Agile transformation, application of technologies, and more. is the largest Agile conference in Central Europe. PMO London 2024 June, 18-19.
I’ve been thinking more about possible measurements in an agile transformation journey. The first Possible Measurements post focuses on product throughput measurements. This post will focus on measurements you might see when the culture changes with an agile transformation. Again, do start with your why. Do join us.
I was clever in the title for my Is Your Product Owner an Overloaded Operator? Many product owners are technical. I could have used a different title, such as “Product Owners: Overloaded and Underappreciated,” and helped my ideal readers feel smart. My title confused some of my ideal readers. Not confused.
Introduction to an Agile Transformation series… I’ve seen several agile transformation challenges. Since I want to address those challenges, this is a series of posts about agile transformation. The problems I’m planning to address are: Understanding why agile, why now. You might have another reason.
My updated writing workshop. If I wait too long to complete some of these, such as the updated writing workshop or some of the slides, I won't be able to deliver them when I want to. The post How I Manage My Product Development: Ease with Continuous Flow (Day 1) appeared first on Johanna Rothman, Management Consultant.
Let's imagine a 6-person team: 3 developers, 2 testers, one product owner. Mondays and Wednesdays, the product owner, one developer, and one tester are in the office. When Mark and I wrote From Chaos to Successful Distributed Agile Teams, we saw these satellite team traps: People in the office forgot about the people not in the office.
Marketers need to master data analytics, customer experience, and product design. This includes the product, the buying process, the ability to provide support, and customer relationships over time. Today, creative marketers need to operate more like entrepreneurs, continuously adjusting to sustain “ product/market fit.”
And at Greycroft, a venture capital firm, investor Teddy Citrin has laid out a veritable map for the further disruption of every consumer products category. Plug-and-play e-commerce technology, search engine optimization, and other distribution solutions are making it ever easier for products to directly reach consumers.
As a consultant, I create many kinds of information products: both writing and speaking. That allows me the most flexibility in my product development. However, too many organizations don't differentiate between what they need to ship as experiments and when to finalize the product.
Agile transformations are tough. That’s because wherever you start, the agile transformation creates culture clashes. Often, teams start with agile approaches. Teams discover the agile approach and practices that work for that team. That’s the external part of what we see in an agile transformation.
One of my clients has many reasons for wanting an agile transformation. Their old products are at the end of their lives. They need agile approaches so they can get feedback from customers as they develop the new products. Agile approaches are perfect for their corporate needs. Their agile transformation is stuck.
Agile culture is about the ability to change. You need to know why you want to change, but once you know that, agile cultures promote change.). We (as agile teams and organizations) deliver something to get some feedback and learning. You might work for one of these companies and they want to use an agile approach.
And she wants the teams to create products the customers want to buy. Jenny has experienced what many of you have, too: Collaborative teams with diverse experiences can develop products customers want to buy. Over her career, Jenny has learned that it's easier to sell more product than to manage costs. Learn with Johanna.
As their organizations move to agile approaches, these managers have problems: their organization (managers above them) wants to measure them by the old rules which demand control. ” Too often, managers feel this tension because the agile approaches challenge the organizational culture. Ask for the results the manager wants.
A colleague unfamiliar with lifecycles or agility asked, “How can we use sprints in this approach?” Every sprint delivers working product.” 30-minute timeboxes to do a draft of a workshop. See Create Your Successful Agile Project for more details.). They do have product goals. ” “Oooh.”
When I teach the project portfolio management workshop, we spend a good chunk of time getting all the projects down on cards and then organizing them. But because everyone felt pulled in too many directions, they needed to make some decisions now , even before a portfolio workshop. We decided to gather some data about their WIP.
” is one of the questions I see when I work with people going through an agile transformation. I like to see the questions reflect the why for your organization’s agile transformation. A simplistic qualitative measure of organizational agility). “What should I measure???” What do we want less of?
In addition, a product leader might approve the feature. Finally, the team, a product leader, or the customer(!) But if you are similar to one of my long-ago clients, they could plan on too many defect escapes every time they released another version of the product. See What Lifecycle or Agile Approach Fits Your Context?
Notes from previous workshops I wanted to integrate when I updated those workshops. Over the past year, as I realized the pandemic would probably change what and how I offered for workshops, I've slowly recycled or filed all that paper. The ideas for updating the workshops, not the notes themselves.
The leaders in the Facilitative Leadership Workshop faced the following challenges: High expectations to take, promote, and encourage a cross-functional and program focus vs. the predominant product and function focus that most of their internal customers follow and are rewarded for.
Especially when we use agile approaches, we want to be close to our customer. Most of their customer information comes via a product owner, who learns from a product manager. Most of their customer information comes via a product owner, who learns from a product manager. That's an awful lot of the telephone game.
If you're trying to write a proposal for a conference or have an agile story you want to tell, consider framing the story this way: Start with the problems. For an experience report, consider adding the initial state (x many teams, y products). I'm working on an agile management talk proposal. What kinds of problems did you see?
You want to present a talk, workshop, experience report at a conference. (Or, I got the idea for this series from Chris Murman's talk at Agile 2019 and from all my shepherding for the Agile 20xx and XPxx conferences. (If For example, I only offer talks for people using agile approaches or trying to. Not for work.
We taught them very simple strategies to build renewal into their lives, and they left our workshops eager to change the way they worked. More recently, we worked with the senior team of a large consumer product company which had been severely disrupted by smaller, more agile online competitors selling their services directly to consumers.
I spoke with an agile coach whose team works in flow, similar to this board. The column on the left, “Stories to Workshop” is their backlog refinement column. Especially on the Workshop column. Their product owner doesn't spend enough time with the team. We don't have an agile roadmap.
We organize all of the trending information in your field so you don't have to. Join 55,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content