MS SharePoint as a Wiki: Few Functions, less Compatibility

The basis for this article were recently constructed under the leadership of Martin Seibert at an open-space session at the WikiSym in Portugal. The original document is available in English under the title “How good is MS Sharepoint as a wiki?”

Without professional knowledge management, companies are losing potential, wasting resources, and acquiring unwanted competitive disadvantages. Along with many other companies, the industry giant Microsoft has rolled out its own application, SharePoint, which allows data to be centrally deposited and edited.

99 Reasons for Scrum: How service providers benefit from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. In the last two articles, we explored how the customers and how staff benefits from Scrum. The last article lists the benefits of Scrum projects for service providers:

99 Reasons for Scrum: How staff benefits from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. In the last article, we explored how the customers benefit. This article focuses on the benefits of Scrum projects for staff:

99 Reasons for Scrum: How customers benefit from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. First, let’s take a look at the benefits for the customer:

Diagrams in Confluence and JIRA: draw.io versus Gliffy

draw.io allows the creation of a diverse range of diagrams within Confluence and JIRA via an intuitive and responsive interface. Possible diagrams are flow charts, network diagrams, org charts, UML diagrams, mind maps and many more. draw.io is based on a market leading diagram technology that has been developed by JGraph in 2005 and therefore has matured a lot by now. In 2012 the application draw.io was created and is available as a plugin on the Atlassian Marketplace, directly offered by //SEIBERT/MEDIA.

Challenges of migrating a company wiki to Confluence and why it is worth overcoming them (part 2)

Companies that want to convert from their current company wiki system to Confluence must overcome a few challenges: existing users are used to working with the platform, changing systems always involves trade-offs, and transferring existing content is complex and painful. In the previous article, we described these common challenges in detail. In this article, we will explain why the switch to Confluence is still a good idea and why the exhausting migration process is still worth the effort.

Challenges of migrating a company wiki to Confluence and why it is worth overcoming them (part 1)

If you take a closer look at the various company wiki systems available on the market and objectively evaluate them, you will likely come to the conclusion that Confluence by Atlassian is the best and most sophisticated solution out there. Often, such comparisons are made when a company already uses another wiki – a system that grew organically beyond a department, an open-source system introduced as a trial run, or consciously chose the Wikipedia system MediaWiki because it’s the most successful software of its kind.

The advantages of pair programming

In agile software projects, it goes without saying that the developers work together. Scrum is, after all, based on teamwork. In most cases, however, each programmer works alone in front of their screen. The concept of pair programming is different because it pairs up two programmers who then together work on the same task, taking turns who sits at the keyboard. Customers unfamiliar with the pair programming idea might think this is some sort of job creation program: Why should we pay for two developers to work on a task that one programmer could do alone? This would only make sense if it cut development time in half, but that is most certainly not the case. No, this is indeed not the case. But how does pair programming benefit customers then?

Reasons why you as customer should test your new software intensively and at an early stage

The core of agile software development according to Scrum is regularly releasing product increments to the customer. The software’s functions are gradually extended, but the customer receives a version of their software right after the first sprint. That’s why at the end of each sprint, a review meeting is held where the development team presents the new functions to the customer. In this article, we will explain why it makes sense for the customer to participate in the reviews and why they should test the software created for them intensively and at an early stage.

Any Questions or Feedback? Contact us now!

Fill out my online form.
Um unsere Webseite für Sie optimal zu gestalten und fortlaufend verbessern zu können, verwenden wir Cookies. Durch die weitere Nutzung der Webseite stimmen Sie der Verwendung von Cookies zu. OK Details