Consulting:Meßtechnik Dokumentenarchiv

The Meßtechnik Dokumentenarchiv (MTDA) is a database and web application that replaces paper files in your organization.
SCHOSTE.COM provides the planning, implementation, maintenance, extension and consulting for this product of the Meßtechnik GmbH & Co KG.

MT Dokumentenarchiv start page

All paper files are pre-processed and tagged with a bar code. These documents are then put aside for scanning. Once they have been scanned the application puts them into the virtual document archive (as PDF-files). Employees and co workers can access these documents any time, find them by searching for key words and read them online. This way a physical paper storage is replaced. The same file can new be read (and modified) by multiple persons at the same time.

In this application bar code recognition and bar code creation is done.

Information from different sources are processed. Among these processes there is the automatic processing of PDF-file of third party applications, as well as the automatic processing of Microsoft Office files (Excel work books, Word and Outlook files).

The application is available in English, German and Albanian. It can be quickly translated into other languages on demand.

SCHOSTE.COM did the planning, the implementation the quality assurance and service after delivery. Small features are planned and implemented. After several iterationen (Sprints) they integrated to a wholistic solution. These features are developed modular and with regards to extensibility. After every iteration the client can experience the new features in action and request changes if necessary. This development approach is transparent and helps to reduce costs, since no unnecessary functionality is developed.

Quality is assured by automatic regressions tests. This way a delivery of the application in different, stable versions is possible any time.

SCHOSTE.COM also provides a Service Call Tracker as service and offers 3rd-Level support to the customers. If issues come up they are dealt with quickly and effective. Change requests are coordinated this way too.

MT Dokumentenarchiv service chain

For more information about the MT Dokumentenarchiv visit the web site.

 

Consulting, Scrum:Release Planning Meeting

SCHOSTE.COM is Scrum.org certified and offers support when introducing agile processes (like Scrum) in your software development teams.

We accompanied that team of the AVL List GmbH that created and works on the successful product CRETA - a calibration data management software. In an agile software development process similar to the Scaled Agile Framework (SAFe) - a software development process designed for big enterprises - multiple teams with dependencies to each others are planning the upcoming development iteration in a so called Release Planning Meeting (RPM).

Product Management Presentation Team Break Outs CRETA Team Break Out Draft Plan Review CRETA Team

In a usual Sprint Planning Meeting a team plans the coming Sprint by moving User Stories from the Product Backlog into the Sprint Backlog. In the RPM multiple teams of one Release Train plan the coming Iteration, consisting of multiple Sprint, by transforming features from the Feature Backlog (in SAFe the Program Backlog) as User Stories into the Team Backlog

The Team Backlog is filled for all Sprints of one Iteration (four Sprints plus one innovation Sprint) so that it is visible when which feature is going to be completed during the Iteration.

After the planning there is the so called Draft Plan Review. Product Management of the Train looks at the plan of every team. Questions about the plan and the content can be asked. This ensures the dependencies of the teams have the focus they need.

Quality:Test Driven Development

Quality assurance in software development doesn't start after implementation. It should be a part of the plan already. While implementing it should be present and finally it should be automated.

In this presentation (currently only available in German) we show how develop in C# with Microsoft Visual Studio and TFS in a test driven way. It illustrates that tools only do not mean test driven development. A change in the approach and the way how coding is done is required.

The huge advantage of this way of developing is that an (almost) complete test coverage of functionality is created implicitly. Misunderstandings of requirements and errors in the implementation are usually discovered before it is delivered to the customer.

Additionally to the video there is a practical example to experience the presented way of development.