Keeping tabs on Microsoft is a full-time job. Microsoft technologies, roadmaps, and licensing policies never stop changing and the pace of this change keeps accelerating. DOM is the only independent organization in the world devoted exclusively to tracking Microsoft. We've been doing it for nearly three decades. No one understands Microsoft better than we do.
Unmatched expertise. Our analysts attend dozens of conferences, talk with Microsoft customers and partners, tear apart hundreds of user manuals and SDKs, and meet with Microsoft technologists and managers on a regular basis.
It's a painstaking process that allows us to help you spot the new Microsoft technologies and shifts in strategy that merit your attention—and avoid those that don't. Independent and impartial. We are an independent company. Our customer base includes Microsoft largest customers.
Microsoft is not an investor in our company. Microsoft does not underwrite any of our research. Microsoft does not purchase any advertising in our publications we carry no advertising. Microsoft does not exert any editorial control. You need DOM if:. You plan, build, or manage systems that use Microsoft products and services. DOM delivers hard-to-find details you need to extract maximum value from your Microsoft purchases. You manage your organization's Microsoft licensing agreements.
DOM helps you to understand the best way to purchase the licenses you need and how to stay compliant without overbuying. We will not make your information available to anyone else at any time. For a complete description of DOM's privacy policy, please click here. Skip to main content. Should I target the current product release for my development or deployment? Or, should I wait until the next planned version? At what point will diminished support for product versions I currently rely on compel me to consider migrating to a newer version?
In-depth reports drill down into key Microsoft technologies and initiatives so you understand the technical significance and strategic underpinnings that can affect your business. Published bi-monthly, reports cover vital areas including: Development platforms Licensing policies and technologies Security infrastructure Systems management Server applications News and Analysis. An all-in-one-place resource that keeps you up-to-date on the full breadth of Microsoft activities. Published online each week and in print every month, their comprehensive Update news and analysis service covers all aspects of Microsoft-including operating systems and server apps, development tools and programs, desktop applications, appliances, online services, licensing, organizational shifts, marketing and sales initiatives, and much more.
For each new Microsoft product, technology, policy, initiative, and strategy, Directions answer: How does it compare with its predecessor? What's actually new? Is it consistent with what other parts of the company are doing? Where is it headed? How will it affect customers, partners, and competitors?
Connecting your product strategy to implementation drives alignment and keeps everyone focused on the work that matters most to achieving the vision. You can visually communicate the direction of your product to internal teams and external partners. Visibility into what is coming next helps the entire organization prioritize and plan for the new experience you will deliver. Your work as a product manager impacts other groups, and you need their input and participation to deliver a Complete Product Experience CPE.
This is why the best product roadmaps include cross-functional teams and factors. For example, marketing can prepare for more impactful launches and campaigns, IT can improve the overall technical infrastructure, and sales can better set customer expectations.
The more inclusive your roadmapping process is, the greater organizational alignment and support you will have when you release that new experience. Before building your product roadmap , you must know the business goals that your efforts will support and define the initiatives you will invest in to support those objectives.
Once you have a high-level product plan, you can decide which releases and features are best aligned, then visualize it all on a timeline.
What you show on your roadmap depends on your intended audience. For example, t he leadership team will want to understand the strategic importance of what you will deliver, conveyed through roll-up relationships between major releases and associated goals and initiatives.
Customers, on the other hand, will be more interested in seeing the theme of the release and any critical functionality they need. And of course, you would not likely want to show more detail than that anyway. For example, you might choose to show an external release date to customers that is different than your internal release date.
Or you might use a broader time frame e. Your product roadmap will also reflect the development methodology that your organization follows. For example, an agile team will create a roadmap that is incremental and flexible to accommodate changes in customer needs and the market.
This differs from a roadmap developed by an organization taking a traditional waterfall approach. A waterfall product roadmap is more fixed — it conveys a long-term commitment to building specific features within a given time frame. Step 1: Define the strategy Strategy is the "why" of what you will build.
Set the vision, goals, and initiatives for your product and how they will support overall business objectives. A strong product vision captures the crucial information the team must understand to develop and maintain a competitive advantage. This includes details of who your customers are, what they need, and how you will go to market with your offering. Step 2: Review and manage ideas The best way to consider customer requests is to rank each one. You can do this by scoring ideas comprised of metrics that reflect your strategy.
Scoring takes subjectivity out of the idea evaluation and allows the ideas that have the most significant impact to rank higher in priority. Step 3: Define features and requirements If strategy is the "why" then features are the "what" — the "how" is for your development team to determine.
Identify the specific features that best support your strategy. Build those out into user stories and detailed requirements that give engineering teams the context they need to implement the best solution. Step 4: Organize into releases Now you are ready to organize those features into themes.
Agile teams may also use epics to organize major work efforts. Once you have everything sorted, you can set timing for releases. These can be grouped according to a specific launch or your development capacity. Step 5: Choose a view For each roadmap you create, customize the types of information and level of detail you want to include.
Consider the following questions:. Roadmapping helps you capture and communicate your product plans. As already noted, audience is a major factor in what elements you present and how.
You can decide which components to include based on what you want to convey — product, goals, initiatives, releases, epics, features, and more. Here are four common types of product roadmaps:. Portfolio roadmap. A portfolio roadmap shows the planned releases across multiple products in a single view.
This is useful for providing a strategic overview of your plan to executives or advisory boards. It can also help internal teams understand how their specific projects relate to the work of other teams. A strategy roadmap displays the initiatives or high-level efforts that the team needs to invest in to achieve the product goals. It is great for presenting your initiatives to executives and giving internal teams an understanding of how different releases contribute to the overall business strategy.
A releases roadmap communicates the activities that must happen before you can bring the release to market — what needs to be done, when, and who is responsible for delivery. This is helpful for coordinating release activities with other cross-functional teams, such as marketing, sales, and customer support.
A features roadmap shows the timeline for when new features will be delivered. My personal data in respect of which the consent is given, include: name, surname, patronomic, gender, position, data on employment, official position, contact details phone numbers and e-mail address, foreign language skills.
I acknowledge that Microsoft Rus LLC will only process the data as long as necessary for the particular purpose involved and might ask me to renew my consent for the processing after 5 years to ensure it follows my intent.
Please read the Microsoft Privacy Statement. Please resolve the following errors before submission:. Request a call. Thanks for requesting a call A sales representative or Microsoft partner will be in touch within four business days. Community Engage with experts and peers, and find local events. Join in. Blog Read the latest news, tips, and insights for modernizing your business. Read the blog. Documentation Find resources for users, developers, and IT professionals.
0コメント