Skip to main content

Bertrand Duperrin's Library tagged topdown   View Popular

17 Sep 09

Going beyond the hype: Identifying Enterprise 2.0 best practices

Those trying to read the tea leaves about Enterprise 2.0 these days can see that the software at least has arrived in a bare majority of companies, even if it’s just Facebook or Twitter across the firewall. Genuine adoption and meaningful integration into business processes has certainly happened in a number of organizations, but is still the edge case today rather than the rule. That’s not to say the current case studies aren’t reporting gains, they generally are. But the message here is that many enterprises are now actively in full contact with the social computing world, whether they want to or not, and now it’s time to understand how to deal with the benefits and issues.

blogs.zdnet.com/Hinchcliffe - Preview

enterprise2.0 adoption socialcomputing framework bestpractices communitymanagement costs trust risk bottomup topdown control

16 Sep 09

Top-down and Bottom-up Project Management: Leveraging the Advantages of the Two Approaches

Significant changes are taking place in management and especially project management today. We hear that organizations, like the New York Times, Tribune Co., Ernst & Young switched from the so-called top-down management style to bottom-up management. Others, including some of the world’s biggest corporations, such as Toyota and IBM, implemented bottom-up management style elements in some of their departments. The popularity of the bottom-up approach to management is growing. In spite of this fact, the discussions about the two major approaches are still hot. Why have organizations become so anxious about changing their management style? If we compare the two management approaches, the answer to this question will be clear.

blog.softwareprojects.org/p-down-and-bottom-up-1936.html - Preview

projectmanagement topdown bottomup management project participation collaboration enterprise2.0 projectmanagement2.0 collectiveintelligence

  • . Team members are invited to participate in every step of the management process. The decision on a course of action is taken by the whole team. Bottom-up style allows managers to communicate goals and value, e.g. through milestone planning. Then team members are encouraged to develop personal to-do lists with the steps necessary to reach the milestones on their own.
  • These methods include are Enterprise 2.0 technologies – wikis, blogs, social networks, collaboration tools, etc. They come into organizations and change the original way of executing projects. They turn traditional project management into Project Management 2.0 and bring new patterns of collaboration, which are based on collective intelligence. Collective intelligence is a collection of valuable knowledge from different fields that each project team member is an expert in. This knowledge is now successfully collected and shared shared in a flexible, collaborative environment brought by second-generation project management software. The project manager is the one to conduct the work of his team and choose the right direction for the project development, based on the information received from the individual employees.
17 Aug 09

Gartner Identifies New Approach for Enterprise Architecture

“The first key characteristic of the emergent approach is best summarised as ‘architect the lines, not the boxes’, which means managing the connections between different parts of the business rather than the actual parts of the business themselves,” said Bruce Robertson, research vice president at Gartner. “The second key characteristic is that it models all relationships as interactions via some set of interfaces, which can be completely informal and manual – for example, sending handwritten invitations to a party via postal letters - to highly formal and automated, such as credit-card transactions across the Visa network.”

www.gartner.com/...page.jsp - Preview

architecture enterprisearchitecture IT ITdepartment topdown

08 Feb 09

émergenceweb : blogue » Dessine-moi un intranet 2.0 : Un cas de bonne gestion du changement…

Si vous gérez l’intranet et l’introduction d’outils Web 2.0 dans votre organisation et en particulier la couche de «business social software», désolé les ami(e)s mais le «bottom-up« et le «patchwork organique» ne fonctionnent pas… «Bottom-up can’t be managed» comme disent nos Voisins du Sud. Vous êtes surpris ? Pas très 2.0 comme attitude non ? Faut être réalistes ici. Monter une stratégie d’intégration de tous les outils technologiques qui composent le coffre à outils d’une stratégie «entreprise 2.0» ne peut attendre l’intégration organique surtout avec un budget et des échéances à gérer…

emergenceweb.com/blog - Preview

enterprise2.0 adoption integration bottomup topdown casestudies pennstateuniversity outreach socialsoftware communication change changemanagement

1 - 4 of 4
Showing 20 items per page

Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »

Join Diigo