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
We all have the tendency to look at other cultures through the lens of our own. In my experience working and teaching across cultures, I’ve noticed one important area where this frequently causes conflicts: deadlines. Western cultures tend to view time as linear , with a definitive beginning and end. Pamela Hinds.
When I work with these teams or their managers, I realize they're not demoing or retrospecting on a regular basis. That creates distrust and an anti-agile culture. And all those ways require we change the culture from that of resource-efficiency thinking to flow-efficiency thinking. That's a cultural change.
Demo on a regular cadence. An agile approach will work better, but an agile approach is a cultural change, which you might not need.). Which means you can demo at will. Demo Early and Often. In addition, create a cadence for demos, such as Wednesday morning at noon or just before. Record the demo.
” For years, I explained that the more often the team or program could demo, the more the project or program could engage its stakeholders. See Customers, Internal Delivery, And Trust for a recent post about demos and trust.) The more frequently you can demo, the more your partners can trust you to deliver something.
Instead, I see assumptions that reveal a divide-and-conquer, and possibly a command-and-control culture, not an agile culture. See How to Start Thinking in Flow Efficiency for Better Teamwork & Throughput and What Does Your Culture Value: People “Efficiency” or Work Throughput? When was the most recent demo?
Her ideal readers are the teams doing the work, so they can change their demos and reporting frequency. As a company, we need more demos and more data. However, we all need to see weekly demos according to the attached format. Please ensure your demo is ready every Wednesday by noon Eastern. Was Polly a little snarky?
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. What about those cultural changes? And once you release regularly, you can deliver and demo that often.
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. This can work well if you demo something at least monthly once you start writing code and tests. But that's the value of the demo.
Because the “teams” couldn't deliver something small, they didn't demo very often. Over months, they stopped demoing anything. Because no one saw any demos, management couldn't trust the teams to deliver. Then, the managers asked the teams to demo something every week instead of measuring schedule variance.
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. Organizational culture.
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. That's because agile approaches require the organization to change its culture. They want an agile approach, so they started with Scrum. What About Other Lifecycles?
Here are some examples: Demos, even of partially working product. It might not be a customer-worthy demo, but it's a demo of a sort.). See Three Collaboration Secrets to Create Your Agile Culture.) If your team is still learning how to work as a team , consider the ideas in Visible Progress. Tip 3: Reduce the Team's WIP.
I like demos to know when if we're on track. Demos can also tell us if we're getting close to done. Demos can tell us if we've done enough. .” The teams are moving to an agile culture. It's more likely the manager has not yet changed his/her beliefs and values to those of an agile culture. Help them learn.
Once our customers saw demos, they wanted to change things. However, if you use cross-functional teams, Evolutionary Prototyping shines as a way to reduce risk, especially if your company can't develop and maintain an agile culture. The blue lines are the feedback we expected. I know, what a surprise. Part 1, Serial Lifecycles.
When organizations lack a formal innovation pipeline process, project approvals tend to be based on who has the best demo or slides, or who lobbies the hardest. Organizational debt is all the people and culture compromises made to “just get it done” in the early stages of an innovation project.
See and demo the product as it grows. If your company can't create an agile culture, consider an incremental lifecycle, especially if you have schedule risks. Release as often as we have finished features. End the project whenever we want to. This addresses schedule risk.).
This team started off with a serial lifecycle, so they didn't even plan to have a demo until about September or so. I chose to add more testers and writers and increase the team's collaboration so we could see a monthly demo. Now, the tester was 6 months behind. At the time, I did not realize I reduced the WIP.
Ask for a regular cadence of demos, too. The more often you see a demo, the more often you can see the team succeed. I offer many possible options for measures in Create Your Successful Agile Project. Two of them are the product backlog burnup and the feature chart in Velocity is Not Acceleration.
Nor do the teams demo on a regular basis. The feedback loops helped the teams create smaller features, which allowed the teams to move to weekly builds and demos. These clients are starting to create culture change with internal deliverables, even though their customers can't take and don't want weekly deliverables.
To account for its success, many point to America’s entrepreneurial culture, its tolerance for failure and its unique ecosystem of venture funding. Eric Haller, EVP and Global Head at Experian Data Labs emphasizes creating a culture of discovery. ” Bridge the cultural divide. ” We need to move faster.
Not only does each team have all the skills and capabilities it needs, but the product line has all the skills and capabilities it needs to manage the culture. Instead, the projects used a staged-delivery life cycle , an incremental approach with cross-functional teams and monthly demos. That includes product ownership.
Here are some examples: Demos, even of partially working product. It might not be a customer-worthy demo, but it's a demo of a sort.). See Three Collaboration Secrets to Create Your Agile Culture.) If your team is still learning how to work as a team , consider the ideas in Visible Progress. Tip 3: Reduce the Team's WIP.
Because your context is unique to you, your team, project, product, and culture. And, with any luck, nudges the culture in a good direction for your team, project, and product. Why Do You Want an Agile Culture for Your Product? Notice I said the culture is for this particular product. What do you need?
This post is about what you can do to create an agile culture, regardless of where you are in the organization. BTW: One more thing about an agile culture: Many of the people I spoke with at the conference are convinced they need to “scale.” And, they change the culture to one that supports agile approaches.
They more often use flow with various cadences of planning, demos, and retrospectives. That's now, where I rarely see an agile culture. Maybe if I saw an agile culture we wouldn't need that separation.). She is a servant leader for the team. If the team uses Scrum, she might be a Scrum Master.
Demo inside the organization. But they learn as they: Prototype and ask for feedback. Conjecture about an architecture or an algorithm, and test their theories. Build, as in compile, and create a usable version. Release outside the building for customer feedback. Other people think all we do is type and build.
This culture shift ripples down from the top and what often felt like a company on a mission to change the world now feels like another job. As process oriented as the new CEOs are, you get the sense that one of the things they don’t love are the products (go look at the Apple Watch announcements and see who demos it).
Dan Lyons’s book Disrupted is an often-delightful tour through startup culture, based on the author’s experience working at online marketing firm HubSpot. Despite taking the faux-curmudgeonly attitude of an anthropologist exploring the strange world of business dudes — is a sales funnel really that much of a novelty?
And because every sales team has a unique sales strategy, culture, solution, and definition of winning, the best sales playbooks are unique to each organization and target buyer persona. Sales Culture. Do not underestimate the need for the right sales culture to meet your targets. Sales Talent.
Project lifecycles and cultures manage all those risks. And, you can decide if you want to try to change the culture. Or, you might only need informal demos to show people where you are. You might show other people internal demos. You don't have to change your culture to use any lifecycle. You'd like to experiment.
The closer to the left your products are, the more your managers might be open to changing their behaviors and the culture. TL; DR: “Stop making it harder” is a culture problem. However, note that the corporate Culture (Big-C-Culture) was that they could take advantage of women. The closer to the right?
Some of the dysfunction was due to the culture, which discouraged collaboration. That's when the culture of experience spat in my face. Culture Trumps Everything Up until I arrived, the “team” culture was anti-collaboration. Then, senior management offered kudos when we showed a demo.
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