InterLogistika Exhibition is an inter-industry, interdepartmental, interregional and common exhibition area, which resolves the tasks of development of transport & logistics potential of Russia and integration of the country into the global economic space.
9/9/2024 - 9/11/2024 Los Angeles CA, United States
...
Hispanoamérica
Work at ArchDaily
Terms of Use
Privacy Policy
Cookie Policy
Winning Team Announced for Moscow Expansion
Written by Karissa Rosenfield
Published on September 13, 2012
An international jury has selected Capital Cities Planning Group (CCPG), an Anglo-American team including Gillespies, John Thompson & Partners and Buro Happold, as winners for the design and planning of the new Federal District in Moscow.
Earlier this year, the Russian Federal Government announced that it was doubling the territory of Moscow to enable it to grow into a competitive 21st century world capital. In response, Genplan, Moscow’s city planner, earmarked an area of 155km2 to the south-west of the city for a new Federal Government Centre, aiming to relieve inner-city congestion through the relocation of the capital’s major employer. Ten international teams were invited to develop strategies and designs for the region during a six month, three stage competition. Continue reading to learn more.
CCPG’s winning proposal calls for a new ‘City in the Forest’ for 1.7 million people, providing 800,000 new jobs with a focus around the ‘Triple Helix of Government, Education and Business’. The new layout reconfigures the 155 km2 territory for the district and looks to create an integrated, properly-planned urban hierarchy served by a transit-orientated movement system.
The design features a new mixed-use capital district configured around a series of lakes designed by the UK Landscape Design Practice Gillespies. Brian Evans, partner in charge of Gillespies Glasgow Office, who led the British side of the team said: “We are all knocked out by this recognition for our work on the world stage. It seems that our design to use the natural topography of the site to create a series of lakes as the setting for the new Federal District was one of the key factors in the jury’s mind when they appraised the different proposals”.
John Thompson, Chair of John Thompson & Partners & Honorary President of the Academy of Urbanism, said: “We are delighted that our team has won the competition for the design of the new Federal District, bringing together international best practice to create a model for the further expansion of Moscow through the creation of a properly serviced, zero-carbon, transit orientated urban hierarchy set within a forest and lakeside landscape.” Additionally, the jury has awarded Antoine Grumbach & Jean-Michel Wilmotte of Paris for the overall planning of Moscow.
The jury was headed by Deputy Mayor of Moscow Marat Khusnullin. The panel also includes the president of the Union of Architects of Russia Andrey Bokov, Dean of the Graduate School of Urban University “Higher School of Economics” Alexander Vysokovsky, Spanish urbanist Alfonso Vegard, curator of the “Greater Paris” Maurice Leroy, Advisor to the Minister of Transportation and Vuk Vuchik member of the Berlin Chamber of Architects Hildebrand Mahlyaydt.
The Capital Cities Planning Group are:
Urban Design Associates, Pittsburgh (USA)
Beasley & Associates, Vancouver (Canada)
Gillespies, Glasgow, (UK)
John Thompson & Partners, London (UK)
Nelson Nygaard, San Francisco, (USA)
Buro Happold, Glasgow (UK)
Group Ark, Moscow (Russia)
Solving Efeso, Abu Dhabi (UAE)
Prof Stuart Gulliver, University of Glasgow (UK)
The 10 teams competing were:
Ostozhenka (Russia)
Architectural design workshop Prof. AA Chernikhov (Russia)
Moscow Architectural Institute (State Academy) (Russia)
TSNIIP urban (Russia)
MARCHI (Russia)
Antoine Grumbach et Associes/Jean-Michel Wilmotte et Associes (France), LAUC (France)
OMA – Office for Metropolitan Architecture (Netherlands)
Ricardo Bofill (Spain)
Studio ASS SECCHI – VIGANO (Italy)
Capital Cities Planning Group – Urban Design Associates (US/UK)
Image gallery
Sustainability
世界上最受欢迎的建筑网站现已推出你的母语版本!
想浏览archdaily中国吗, you've started following your first account, did you know.
You'll now receive updates based on what you follow! Personalize your stream and start following your favorite authors, offices and users.
Integrations
Learning Center
MoSCoW Prioritization
What is moscow prioritization.
MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique for managing requirements.
The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won’t-have, or will not have right now. Some companies also use the “W” in MoSCoW to mean “wish.”
What is the History of the MoSCoW Method?
Software development expert Dai Clegg created the MoSCoW method while working at Oracle. He designed the framework to help his team prioritize tasks during development work on product releases.
You can find a detailed account of using MoSCoW prioritization in the Dynamic System Development Method (DSDM) handbook . But because MoSCoW can prioritize tasks within any time-boxed project, teams have adapted the method for a broad range of uses.
How Does MoSCoW Prioritization Work?
Before running a MoSCoW analysis, a few things need to happen. First, key stakeholders and the product team need to get aligned on objectives and prioritization factors. Then, all participants must agree on which initiatives to prioritize.
At this point, your team should also discuss how they will settle any disagreements in prioritization. If you can establish how to resolve disputes before they come up, you can help prevent those disagreements from holding up progress.
Finally, you’ll also want to reach a consensus on what percentage of resources you’d like to allocate to each category.
With the groundwork complete, you may begin determining which category is most appropriate for each initiative. But, first, let’s further break down each category in the MoSCoW method.
Start prioritizing your roadmap
Moscow prioritization categories.
1. Must-have initiatives
As the name suggests, this category consists of initiatives that are “musts” for your team. They represent non-negotiable needs for the project, product, or release in question. For example, if you’re releasing a healthcare application, a must-have initiative may be security functionalities that help maintain compliance.
The “must-have” category requires the team to complete a mandatory task. If you’re unsure about whether something belongs in this category, ask yourself the following.
If the product won’t work without an initiative, or the release becomes useless without it, the initiative is most likely a “must-have.”
2. Should-have initiatives
Should-have initiatives are just a step below must-haves. They are essential to the product, project, or release, but they are not vital. If left out, the product or project still functions. However, the initiatives may add significant value.
“Should-have” initiatives are different from “must-have” initiatives in that they can get scheduled for a future release without impacting the current one. For example, performance improvements, minor bug fixes, or new functionality may be “should-have” initiatives. Without them, the product still works.
3. Could-have initiatives
Another way of describing “could-have” initiatives is nice-to-haves. “Could-have” initiatives are not necessary to the core function of the product. However, compared with “should-have” initiatives, they have a much smaller impact on the outcome if left out.
So, initiatives placed in the “could-have” category are often the first to be deprioritized if a project in the “should-have” or “must-have” category ends up larger than expected.
4. Will not have (this time)
One benefit of the MoSCoW method is that it places several initiatives in the “will-not-have” category. The category can manage expectations about what the team will not include in a specific release (or another timeframe you’re prioritizing).
Placing initiatives in the “will-not-have” category is one way to help prevent scope creep . If initiatives are in this category, the team knows they are not a priority for this specific time frame.
Some initiatives in the “will-not-have” group will be prioritized in the future, while others are not likely to happen. Some teams decide to differentiate between those by creating a subcategory within this group.
How Can Development Teams Use MoSCoW?
Although Dai Clegg developed the approach to help prioritize tasks around his team’s limited time, the MoSCoW method also works when a development team faces limitations other than time. For example:
Prioritize based on budgetary constraints.
What if a development team’s limiting factor is not a deadline but a tight budget imposed by the company? Working with the product managers, the team can use MoSCoW first to decide on the initiatives that represent must-haves and the should-haves. Then, using the development department’s budget as the guide, the team can figure out which items they can complete.
Prioritize based on the team’s skillsets.
A cross-functional product team might also find itself constrained by the experience and expertise of its developers. If the product roadmap calls for functionality the team does not have the skills to build, this limiting factor will play into scoring those items in their MoSCoW analysis.
Prioritize based on competing needs at the company.
Cross-functional teams can also find themselves constrained by other company priorities. The team wants to make progress on a new product release, but the executive staff has created tight deadlines for further releases in the same timeframe. In this case, the team can use MoSCoW to determine which aspects of their desired release represent must-haves and temporarily backlog everything else.
What Are the Drawbacks of MoSCoW Prioritization?
Although many product and development teams have prioritized MoSCoW, the approach has potential pitfalls. Here are a few examples.
1. An inconsistent scoring process can lead to tasks placed in the wrong categories.
One common criticism against MoSCoW is that it does not include an objective methodology for ranking initiatives against each other. Your team will need to bring this methodology to your analysis. The MoSCoW approach works only to ensure that your team applies a consistent scoring system for all initiatives.
Pro tip: One proven method is weighted scoring, where your team measures each initiative on your backlog against a standard set of cost and benefit criteria. You can use the weighted scoring approach in ProductPlan’s roadmap app .
2. Not including all relevant stakeholders can lead to items placed in the wrong categories.
To know which of your team’s initiatives represent must-haves for your product and which are merely should-haves, you will need as much context as possible.
For example, you might need someone from your sales team to let you know how important (or unimportant) prospective buyers view a proposed new feature.
One pitfall of the MoSCoW method is that you could make poor decisions about where to slot each initiative unless your team receives input from all relevant stakeholders.
3. Team bias for (or against) initiatives can undermine MoSCoW’s effectiveness.
Because MoSCoW does not include an objective scoring method, your team members can fall victim to their own opinions about certain initiatives.
One risk of using MoSCoW prioritization is that a team can mistakenly think MoSCoW itself represents an objective way of measuring the items on their list. They discuss an initiative, agree that it is a “should have,” and move on to the next.
But your team will also need an objective and consistent framework for ranking all initiatives. That is the only way to minimize your team’s biases in favor of items or against them.
When Do You Use the MoSCoW Method for Prioritization?
MoSCoW prioritization is effective for teams that want to include representatives from the whole organization in their process. You can capture a broader perspective by involving participants from various functional departments.
Another reason you may want to use MoSCoW prioritization is it allows your team to determine how much effort goes into each category. Therefore, you can ensure you’re delivering a good variety of initiatives in each release.
What Are Best Practices for Using MoSCoW Prioritization?
If you’re considering giving MoSCoW prioritization a try, here are a few steps to keep in mind. Incorporating these into your process will help your team gain more value from the MoSCoW method.
1. Choose an objective ranking or scoring system.
Remember, MoSCoW helps your team group items into the appropriate buckets—from must-have items down to your longer-term wish list. But MoSCoW itself doesn’t help you determine which item belongs in which category.
You will need a separate ranking methodology. You can choose from many, such as:
Weighted scoring
Value vs. complexity
Buy-a-feature
Opportunity scoring
For help finding the best scoring methodology for your team, check out ProductPlan’s article: 7 strategies to choose the best features for your product .
2. Seek input from all key stakeholders.
To make sure you’re placing each initiative into the right bucket—must-have, should-have, could-have, or won’t-have—your team needs context.
At the beginning of your MoSCoW method, your team should consider which stakeholders can provide valuable context and insights. Sales? Customer success? The executive staff? Product managers in another area of your business? Include them in your initiative scoring process if you think they can help you see opportunities or threats your team might miss.
3. Share your MoSCoW process across your organization.
MoSCoW gives your team a tangible way to show your organization prioritizing initiatives for your products or projects.
The method can help you build company-wide consensus for your work, or at least help you show stakeholders why you made the decisions you did.
Communicating your team’s prioritization strategy also helps you set expectations across the business. When they see your methodology for choosing one initiative over another, stakeholders in other departments will understand that your team has thought through and weighed all decisions you’ve made.
If any stakeholders have an issue with one of your decisions, they will understand that they can’t simply complain—they’ll need to present you with evidence to alter your course of action.
Related Terms
2×2 prioritization matrix / Eisenhower matrix / DACI decision-making framework / ICE scoring model / RICE scoring model
Prioritizing your roadmap using our guide
Talk to an expert.
Schedule a few minutes with us to share more about your product roadmapping goals and we'll tailor a demo to show you how easy it is to build strategic roadmaps, align behind customer needs, prioritize, and measure success.
Supply Chain Management: Integrated Business Planning (IBP)
IBP2
Integrated Business Planning (IBP)
The Path to Integrated Business Planning (IBP)
Successful S&OP through Integrated Business Planning
COMMENTS
IBP2
IBP2 is a team of integrated business planning experts with real world experience who recognize that a complete and comprehensive approach is the right path to lasting change. Our service offerings include…. Process Evaluation & Effective Practices. Technology Selection and Solution Architecture. Process Facilitation &.
Working at Integrated Business Planning Associates
Integrated Business Planning Associates. Share details of your experiences. Glassdoor gives you an inside look at what it's like to work at Glassdoor, including salaries, reviews, office photos, and more. This is the Glassdoor company profile. All content is posted anonymously by employees working at Glassdoor. See what employees say it's like ...
Integrated Business Planning Associates (IBP2
View Integrated Business Planning Associates (IBP2 (www.ibp2.com) location in Illinois, United States , revenue, industry and description. Find related and similar companies as well as employees by title and much more.
Integrated Business Planning Associates (IBP2
Integrated Business Planning Associates (IBP2 Profile and History. Integrated Business Planning Associates provides experienced resources committed to helping organizations realize the full power of Sales & Operations Planning (S&OP). We take time to understand your business and the strategic goals for your project, then we apply a ...
Integrated business planning associates (ibp2) Review
Read reviews of Integrated business planning associates (ibp2). Write and share your personal story. Your experience will help others make the right buying decision.
Integrated Business Planning Associates (IBP2) Overview
Integrated Business Planning Associates (IBP2) Information BETA. Headquarters Address: 5313 Washington St, Downers Grove, Illinois. Phone Number: +1 6308815002. Revenue: $0 Million - $1 Million Employees: 11-20 ...
Integrated Business Planning Associates (IBP2) Information
The Integrated Business Planning Associates (IBP2) annual revenue was $1.4 million in 2024. Who is the Managing Director and Vice President Client Delivery of Integrated Business Planning Associates (IBP2)? Chris Karsten ...
Clients
The Coca-Cola company operated with internal silos and decentralized planning processes across its ecosystem of suppliers, which impacted every organization's ability to perform critical material planning. Coca-Cola partnered with IBP2 to pioneer an end-to-end planning process and digitization initiative across its ecosystem of suppliers and ...
Integrated Business Planning Associates (IBP2) Management
Integrated Business Planning Associates (IBP2) employs 23 employees. The Integrated Business Planning Associates (IBP2) management team includes Chris Karsten (Managing Director and Vice President Client Delivery) , Michael O'Brien (Senior Director Strategic Accounts) , and Mike McAlister (Senior Associate) .
Integrated Business Planning Associates (IBP2) Salary
The average annual salary of Integrated Business Planning Associates (IBP2) is estimated to be approximate $92,126 per year. The majority pay is between $80,969 to $104,221 per year. Visit Salary.com to find out Integrated Business Planning Associates (IBP2) salary, Integrated Business Planning Associates (IBP2) pay rate, and more.
Marie Bleuel
Welcome back. ₹. APICS certified Supply Chain Professional (CSCP) with a strong background in customer…. · Experience: Integrated Business Planning Associates (IBP2) · Location: Hemel Hempstead · 498 connections on LinkedIn. View Marie Bleuel's profile on LinkedIn, a professional community of 1 billion members.
Integrated Business Planning Associates
Integrated Business Planning Associates. 4 likes. Consulting agency
InterLogistika 2015(Moscow)
InterLogistika is a unique annually held international exhibition forum, which purpose is to promote development of efficient cooperation between Russian and foreign companies, governmental authorities and private companies in realization of joint infrastructural projects, in implementation of trading & transport, warehousing and other advanced technologies in the field of logistics services.
Winning Team Announced for Moscow Expansion
CCPG's winning proposal calls for a new 'City in the Forest' for 1.7 million people, providing 800,000 new jobs with a focus around the 'Triple Helix of Government, Education and Business'.
MoSCoW method
The MoSCoW method is a prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement; it is also known as MoSCoW prioritization or MoSCoW analysis.. The term MOSCOW itself is an acronym derived from the first letter of each of four ...
What is MoSCoW Prioritization?
MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique for managing requirements. The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won't-have, or will not have right now. Some companies also use the "W" in MoSCoW to mean "wish.".
IMAGES
COMMENTS
IBP2 is a team of integrated business planning experts with real world experience who recognize that a complete and comprehensive approach is the right path to lasting change. Our service offerings include…. Process Evaluation & Effective Practices. Technology Selection and Solution Architecture. Process Facilitation &.
Integrated Business Planning Associates. Share details of your experiences. Glassdoor gives you an inside look at what it's like to work at Glassdoor, including salaries, reviews, office photos, and more. This is the Glassdoor company profile. All content is posted anonymously by employees working at Glassdoor. See what employees say it's like ...
View Integrated Business Planning Associates (IBP2 (www.ibp2.com) location in Illinois, United States , revenue, industry and description. Find related and similar companies as well as employees by title and much more.
Integrated Business Planning Associates (IBP2 Profile and History. Integrated Business Planning Associates provides experienced resources committed to helping organizations realize the full power of Sales & Operations Planning (S&OP). We take time to understand your business and the strategic goals for your project, then we apply a ...
Read reviews of Integrated business planning associates (ibp2). Write and share your personal story. Your experience will help others make the right buying decision.
Integrated Business Planning Associates (IBP2) Information BETA. Headquarters Address: 5313 Washington St, Downers Grove, Illinois. Phone Number: +1 6308815002. Revenue: $0 Million - $1 Million Employees: 11-20 ...
The Integrated Business Planning Associates (IBP2) annual revenue was $1.4 million in 2024. Who is the Managing Director and Vice President Client Delivery of Integrated Business Planning Associates (IBP2)? Chris Karsten ...
The Coca-Cola company operated with internal silos and decentralized planning processes across its ecosystem of suppliers, which impacted every organization's ability to perform critical material planning. Coca-Cola partnered with IBP2 to pioneer an end-to-end planning process and digitization initiative across its ecosystem of suppliers and ...
Integrated Business Planning Associates (IBP2) employs 23 employees. The Integrated Business Planning Associates (IBP2) management team includes Chris Karsten (Managing Director and Vice President Client Delivery) , Michael O'Brien (Senior Director Strategic Accounts) , and Mike McAlister (Senior Associate) .
The average annual salary of Integrated Business Planning Associates (IBP2) is estimated to be approximate $92,126 per year. The majority pay is between $80,969 to $104,221 per year. Visit Salary.com to find out Integrated Business Planning Associates (IBP2) salary, Integrated Business Planning Associates (IBP2) pay rate, and more.
Welcome back. ₹. APICS certified Supply Chain Professional (CSCP) with a strong background in customer…. · Experience: Integrated Business Planning Associates (IBP2) · Location: Hemel Hempstead · 498 connections on LinkedIn. View Marie Bleuel's profile on LinkedIn, a professional community of 1 billion members.
Integrated Business Planning Associates. 4 likes. Consulting agency
InterLogistika is a unique annually held international exhibition forum, which purpose is to promote development of efficient cooperation between Russian and foreign companies, governmental authorities and private companies in realization of joint infrastructural projects, in implementation of trading & transport, warehousing and other advanced technologies in the field of logistics services.
CCPG's winning proposal calls for a new 'City in the Forest' for 1.7 million people, providing 800,000 new jobs with a focus around the 'Triple Helix of Government, Education and Business'.
The MoSCoW method is a prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement; it is also known as MoSCoW prioritization or MoSCoW analysis.. The term MOSCOW itself is an acronym derived from the first letter of each of four ...
MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique for managing requirements. The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won't-have, or will not have right now. Some companies also use the "W" in MoSCoW to mean "wish.".