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
So when does it make sense to customize your agile approach to gain a strategic advantage? They want an agile approach, so they started with Scrum. 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. We do what works.”
By providing real-time insights and streamlining complex workflows, project portfolio management tools empower organizations to handle diverse initiatives with precision and agility. It supports Agile methodologies such as Scrum and Kanban, ensuring adaptability to different workflows.
The teams want to use an agile approach so they can incorporate learning. The managers might even think this is roadmap reflects an agile approach. There's nothing about this roadmap that's agile. You can decide if you need an agile approach. Demo on a regular cadence. The managers want rigid roadmaps.
Back in Part 1 , I wrote about how stage-gate approaches were as agile as we could use at the time. We had one delivery, so our agility was about canceling the project if we couldn't finish it. Barry Boehm developed the spiral model. We develop test plans early. Once our customers saw demos, they wanted to change things.
Opportunities for More Agility. Because we release every time we finish a feature set, we have these opportunities for agility: Re-rank the remaining feature sets. See and demo the product as it grows. You can't just have developers, then testers, etc. What Lifecycle or Agile Approach Fits Your Context?
By providing real-time insights and streamlining complex workflows, project portfolio management tools empower organizations to handle diverse initiatives with precision and agility. It supports Agile methodologies such as Scrum and Kanban, ensuring adaptability to different workflows.
He thought agile approaches would work to “meet” and “enforce” deadlines. In addition, each component team worked on any number of products, both development and support, for any given iteration. However, software product development is not construction. Over months, they stopped demoing anything.
In Effective Agility Requires Cultural Changes: Part 1 , I said that real agile approaches require cultural change to focus on flow efficiency, where we focus on watching the work, not the people. If you and your team have been practicing real agility, you might say these ideas barely show any agility at all. That's fine.
They've started to use agile approaches. There's a great introduction article, Capitalization of software development costs.). Capitalization for Agile Work. Let me walk you through an example of a 5-person agile team. I would add demoing in as value creation, but I'm not sure how accountants categorize feedback loops.
In Effective Agility Requires Cultural Changes: Part 1 , I said that real agile approaches require cultural change to focus on flow efficiency , where we watch the flow of the work , not the people doing tasks. Can you create an agile culture for your team even if you can't change how the organization works? 1,2 and so on.
Many new-to-agile teams use some form of iteration-based agile approach. Back in Time You Spend in Agile Meetings (near the bottom of the post), I enumerated all the possible meetings. I mentioned how you could integrate the demo work into an iteration if you create a column for the demo.
I discussed the origins of the agile approaches in Part 5. In this post, I'll discuss how you can create an agile approach that fits your context. Why should you create your own agile approach? You deserve an agile approach that helps you achieve the business outcomes you need. What do you need? Start with the Team.
That part discusses why managers see agile coaches and Scrum Masters as staff positions, not line jobs. 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.
I started asking if you actually need an agile approach in Part 1 and noted the 4 big problems I see. Part 2 was why we need managers in an agile transformation. Part 4 was about how “Agile” is meaningless and “agile” is an adjective that needs to be applied to something. That would be resilient.
In Costs of an Agile Approach for Hardware Products , I suggested that an iteration-based approach for hardware was too expensive. I focused on the actual development costs. Agile software teams are cross-functional and interdependent. Many agile software teams have somewhere between four and seven people. And, with whom?
A colleague unfamiliar with lifecycles or agility asked, “How can we use sprints in this approach?” Not the thinking and learning that go into the deliverables where you end up with something demo-able, if not usable.” See Create Your Successful Agile Project for more details.). ” “Oooh.”
Its current development is primarily driven by 4 major trends: connectivity, autonomous vehicles, shared mobility, and electrification. As the automotive industry continues its development affected by recent unprecedented disruption, the number of projects its companies take on this year will be increasing.
Successful software product development is about how well the team learns together. See Agile Program Measurements to Visualize and Track Progress and Measure Cycle Time for my suggestions of what to measure. I have more ideas and a more in-depth discussion in Create Your Successful Agile Project.).
One of Rochet’s first tasks was to create a leadership development program that equipped executives with the knowledge, mindset, and ways of working the company would need to grow in the digital age. Help Employees Embrace Agility. Agility is key to success when undertaking digital transformations.
might demo the feature. That defect escaped all your checklists, approvals, and demos. That's because they knew the customers would find problems the development teams had not found. But the development teams? That's because the development teams worked by phase, not by feature. Where Do Your Defects Escape?
After that, they are given access to a simple demo environment with a standard set of configurations, where they can test how our system works. If your company uses other project management tools like Jira, MS Project, or Oracle Primavera, the demo environment will be adjusted accordingly. Data adjustment and integration.
Early on in my agile practice, I believed in generalizing specialists. However, some people thought they could get developers to be system testers—and vice versa. Here's how this might work for your agile team. You don't have an agile team because they're not collaborating on the work. Hooks for logs and demos.
Yes, the premise of my Agile and Lean Program Management book.) I have never seen those three conditions in any non-agile project, but that could be my experience and not universal. That's why many people were interested in the ratio of developers to testers back then. The tester is involved from the start of the project.
In Part 1 , I suggested that when we organize by function, the recognition and rewards might prevent a successful agile transformation. There might be a “centralized” function for these groups, but all the people developing and supporting this product are in the product line. Except, the new development was delayed.
Nor do the teams demo on a regular basis. The teams miss the feedback loops so critical for an agile approach. Their agile transformation falls apart. The developers and testers and anyone else on the product or feature teams. Prevent Agile Projects that Look Like Waterfall. Rethink Your Definition of Customer.
In Create Your Successful Agile Project , I recommend the team end an iteration in the middle of a week. The Wednesday Agenda 9:30- 10 am (or thereabouts) demo the progress the team made. Notice When the Meeting Goes Sideways Meetings, just like the product development, can go sideways. See What's Wrong With Wednesday?
Now, we get to the meat, where the manager needs to know to feel good about the development. I needed to demo more often. This is the same problem as in Want to Be More Effective (and Agile)? The demos build trust—and might offer the team feedback on the product and the product leader feedback on the backlog.
Successful software product development is about how well the team learns together. See Agile Program Measurements to Visualize and Track Progress and Measure Cycle Time for my suggestions of what to measure. I have more ideas and a more in-depth discussion in Create Your Successful Agile Project.).
For years, we've used several metaphors to describe software product development: People-based metaphors, such as: Man-weeks for all the humans working on a project or a product. See Why Shared Services “Teams” Don’t Work with Agility. Demo inside the organization. See People are NOT FTEs.) Worse, the less effective we are.
Agile approaches can help a team release more often. The longer the team goes without a demo, the less replanning anyone can do. When a team releases more often, the product people can replan the product roadmaps. The project portfolio people can replan the project portfolio. Everyone falls prey to “too much” thinking.
Condition 3: Flexible Structure maximizes speed and agility. It’s easy to become enamored with an idea, especially when you’ve invested a lot of time developing it. Condition 4: Purposeful Discovery means testing possibilities to develop user-centered solutions. Fall in love with the problem, not your solution.
Or, you might only need informal demos to show people where you are. Solving Deterministic Problems Does Not Require an Agile Approach. You might show other people internal demos. When the team shows other internal people demos , the team invites trust and greater learning. Why You Might Want an Agile Approach.
Even if a 5 to 7-person team falls into the Everyone Starts Their Own Story trap (see Who’s Playing Agile Schedule Games? or Create Your Successful Agile Project ), the team can still know what's going on. Then, I watched Drunk Agile Episode 75: Team Size. The original architect and developers.) I was wrong.
and Create Your Successful Agile Project. But the demand for software developers was high and I was good. When to give into demands to demo (“I haven't tested!”) Too many managers don't understand the real risks in product development, so they don't know how XP manages many of those risks. Laugh all you like.
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