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
As you walk the show floor, you’ll engage with live demos, product launches, and exclusive offers from over 125 exhibitors. Leadership Exchange : Join the exclusive DevLearn Leadership Exchange to engage in in-depth discussions on strategic leadership, talent management, and developing future leaders.
Several of my clients have internal struggles about how to internally see the future of the product. The managers think they need it “all” instead of using how little thinking to create a product the customers will love. Some possibilities: Assess the product/project risks to choose a lifecycle. What can you do?
See a popular post of mine, “ In Consulting The Process Is An Essential Part Of The Deliverable “ Business plan as a sales document - This situation is particularly appropriate for fund raising (e.g., angels, VCs). technology feasibility, commercial feasibility, ramp-up). for government grants).
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. See Customers, Internal Delivery, And Trust for a recent post about demos and trust.)
I work with elite consultants who, if they don’t have a strong sense of humility, can find themselves angry at potential clients who don’t display sufficient acceptance of the thought leader’s elevated position as he or she observes it in the actions of satisfied clients. I don’t Know your company’s product.
Don’t waste production time. See Jerry’s new speaker demo reel. His consulting practice, founded in 1990, is known for on and off-line Trust-based Consultant Marketing advice that builds businesses, brands and lives of joy. Consulting: [link] Speaking: [link]. Lots of content. Podcasts can be listened to at 2x.
His basic premise was that testing all components of marketing a product was essential to overcome the risks inherent in advertising. That meant looking at product distribution, sampling, copy and graphic split-testing as well pre-empting product specifics benefits and personalities to establish a brand He was a total advertising man.
I had attended a conference on gamifying products in the fall before Covid struck. Somehow we got on the subject of getting through to officials in companies in order to sell our products in the corporate market. See Jerry’s new speaker demo reel. Consulting: [link] Speaking: [link]. A Mastermind. Getting Through.
So they ask the product or project leaders to write a business case for each effort. Because experiments manage risk, we need people with these perspectives to create the experiments: A product leader: someone who can see where the company wants to head with this product. Regardless of the product results for that experiment.
In this part, I’ll discuss an option for a product-oriented organization. Consider a Product-Oriented Organization. Instead of organizing by function, consider a product-oriented organization. Again, I am not saying this is the only way a product organization would look, but this is a possibility. What do you do?
I asked Brad these questions: Do you have product or feature teams that are cross-functional and can release alone? ( Component teams create interdependencies and take much more time to finish work.). Does each team focus on just one product at a time? Schedule Variance Does Not Make Sense for Software Products.
:: Recently I had the opportunity to make a presentation to a small group of consultants; a couple of them worked for Chevron-Texaco. They had just completed a screening process for a multi-million consulting project. 2) Second set of consultants eliminated were CONTENT or FACT CENTERED …they knew everything about everything.
Example 1: Startup/Small Organization with Few Products. They offer their product in two versions: Pro and Lite. The first was not waiting for the end of an iteration to demo or release. They demo'd every week on Wednesday mornings and then they released after the demo. Let's start with a couple of examples. Others mob.
Beau approached us a few months ago to ask about breaking into consulting. He had the epiphany that consulting was his calling in life, and went searching for details – finding MC in the process. We’ve got your resume to go through, and as I gather you have a whole bunch of questions about consulting. Is that right?
High Need for Product Innovation and Change. The more need for product innovation and change, the shorter the feedback loops need to be. When the product requires much innovation and change, management doesn't need estimates. When management sees the product direction, they can say, “Stop with this and continue with that.”
Maybe you want to use this project as a way to integrate a team into a new product or a new domain. Or, you might only need informal demos to show people where you are. Anything else about the current product that affects your solution. You might show other people internal demos. You'd like to experiment.
Every sprint delivers working product.” Not the thinking and learning that go into the deliverables where you end up with something demo-able, if not usable.” They do have product goals. However, they don't deliver value, have team-based planning, a review/demo, or a retrospective. ” “Oooh.”
In Costs of an Agile Approach for Hardware Products , I suggested that an iteration-based approach for hardware was too expensive. Most of the hardware teams I've worked with (inside an organization and as a consultant) have fewer people. Those people work independently until they need to verify the product as a whole, works.
If you're creating products of any kind—especially software products—you've got a team sport. Successful software product development is about how well the team learns together. The better the team learns together, the better the product is. See Product Orientation Requires Technical Excellence ).
I have a new book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. Worse, sometimes the team doesn't demo or deliver. See Manage Unplanned Feedback Loops to Reduce Risks and Create Successful Products.) That's because no product survives contact with the customers.
No one wants to demo this work, because everyone thinks the demo will wander all over the place. Worse, no one wants to demo, because they can't see the value for any user. Use the Demo to Guide Sizing. Use the Demo to Guide Sizing. Start with the demo in mind. I bet you can think of more tests.
It was good to hear how the little golf product company he founded was doing. Marketing Consultant/Start up Consultant. I came onboard because he wanted a marketing consultant. Very quickly I turned into a start-up consultant. tend to take comments about alternatives to the product seriously.
Your team includes all the folks that get credit when the job is done, the objective reached, or the product is delivered. Trust lowers your stress and makes you more productive. That is true whether the business is a product, a service or a combination of the two. See Jerry’s new speaker demo reel. Your Company.
(That might be the feature set or the product. ). ” Many managers now realize they don't have to see everything to get an idea of where the team is going with the product. However, maybe this is a new product for you and you don't quite know how to do that yet. When will we see half of it? That's good.
We had (and still have) too many products to keep the same teams on them for a long time. For programs, the team stayed together and moved to a different feature set/internal product until the program finished. We could move to a new product and/or a new team. My job was to smooth the way for people to deliver products.
I assume you have some sort of functional product development expertise. If not, why are you in technical product development? This post is about your deep domain expertise, first in product, then in agility. First, the product-based expertise. That's often product people, testers, and some UI/UX people.
But there are several problems with all this planning: These plans require prediction at all levels, from strategy to product to what the team delivers. However, too often, the managers prevent product innovations or strategy changes because they planned so much. That's the product. They plan to be able to predict the future.
By product, where they assign a team to a product for a long period of time. By person, where they take one person from here and one person from there, etc, to create enough people to work on the product. Every time the team delivers, the leaders can reassess the ongoing value of the project or product.
I sent a one sheet on my Trust speech and a link to my speaking demo not expecting a response since I was mor interested in their events in major cities across the USA. In part it was because he never stopped tinkering with the product going through at least 5 programmers I was aware of. See Jerry’s speaker demo reel.
The first is that Brooks strongly suggested the idea of a “surgical team” That hierarchical team was a feature- or product-based team. Ten people, seven of them professionals, are at work on the problem, but the system is the product of one mind–or at most two, acting uno animo.”
If you intend to sell beyond your local area and provide services or products you need to have a presence on line. Unlimited products. You can sell as many products as you can invent or purchase whether the product is real world or digital. See Jerry’s speaker demo reel. Consulting: [link] Speaking: [link].
You might have hypotheses about your market, your customers, or how your current product(s) can offer value. Normally, I like to ask the teams who deliver the product to also do the discovery. You might find, as I do, that using flow/kanban with WIP limits and a cadence of planning/demos/retros works better for you.
Back in Part 1 of this series, I explained all the problems I saw with this interview question: “The product owner and dev team cannot decide on a sprint goal, even after hours of discussion. The Wednesday Agenda 9:30- 10 am (or thereabouts) demo the progress the team made. What should the Scrum Master do?” That day needs an agenda.
In addition, a product leader might approve the feature. Finally, the team, a product leader, or the customer(!) might demo the feature. That defect escaped all your checklists, approvals, and demos. Yes, they had to spend time fixing those problems, but they were under no illusions about the quality of the product.
If a celebrity is enthusiastic about your product and endorses it, you could have a winner. If a fan becomes a social media star and brags on your product, you just might have a winner. Amazon changed the pace of delivery across a plethora of product lines. See Jerry’s new speaker demo reel. You could have a winner.
If you are a consultant it is a pretty good bet that you have a profile on Linked In. A photo in the background that shows product(s) you are associated with. Your title Since most consultants are independent professionals operating as solos (nearly 70% in our last survey) you can call yourself anything you like.
I mentioned how you could integrate the demo work into an iteration if you create a column for the demo. Here’s a picture of how you might create a kanban with a Demo state, just before the Done column. Here’s how you walk this board: Start at the column just before Done, the Demo column.
We talked briefly about what I was doing in my Consulting practice working with elite consultants from Singapore to Madrid to make them more memorable and more profitable. See Jerry’s speaker demo reel. Consulting: [link] Speaking: [link]. We would not have been invited if that were the case. And so it goes.
I started this series with many specific concerns about a particular interview question: “The product owner and dev team cannot decide on a sprint goal, even after hours of discussion. Divide and Conquer is Anti-Agility I see the product owner and dev team as a divide-and-conquer approach to work. When was the most recent demo?
I’m a Master of Consultant Marketing. I’ve been doing it since1990 and stopped counting successful new product introductions at 207 and individual branding for consultants at 147 at last count. See Jerry’s speaker demo reel. Consulting: [link] Speaking: [link].
Scientists have found 8 management behaviors that use Oxytocin balance to make people more productive. See Jerry’s new speaker demo reel. His consulting practice, founded in 1990, is known for on and off-line Trust-based Consultant Marketing advice that builds businesses, brands and lives of joy.
When you ask this question, you might learn what some of my clients learned: Sometimes, managers wanted to know when it was safe to announce the product. ” I thought it was reasonable to use data to be able to announce the product. I like demos to know when if we're on track. Demos can tell us if we've done enough.
Let's assume everyone works together, on one project (product, if you prefer). So, let's assume the team spends a total of 4 hours planning, retrospecting, demoing, all that non-creation time out of the 40 hours the team works. I would add demoing in as value creation, but I'm not sure how accountants categorize feedback loops.
Years ago, I consulted with a software company that purposefully hired from the “bottom of the barrel.” They hired me because they were in danger of going out of business due to their inability to release a working product. Instead, tell the manager to create the environment where the team can release the product.).
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