{"id":123,"date":"2016-03-25T13:50:28","date_gmt":"2016-03-25T12:50:28","guid":{"rendered":"https:\/\/rainergrau.com\/wordpress\/?p=123"},"modified":"2016-06-12T07:36:08","modified_gmt":"2016-06-12T05:36:08","slug":"lean-ppm-step-13","status":"publish","type":"post","link":"https:\/\/rainergrau.com\/wordpress\/lean-ppm-step-13\/","title":{"rendered":"Lean PPM \u2013 step 13: Documentation consumer type 3: SW engineers, subject matter experts, technical experts"},"content":{"rendered":"

SW (S<\/strong>oftW<\/strong>are) engineers and experts do not have an interest in documentation. SW engineers as well as experts have an interest in the final solution, especially in a solution that fulfils the needs of the business or users. Unluckily many organizations prevent successfully that SW engineers communicate with the subject matter experts. That\u2019s exactly what agile and lean processes try to address \u2013 to tear down communication barriers to the minimum.<\/p>\n

\"Real

Real Software Engineering Team Spirit<\/p><\/div>\n

SW engineers working in software development have an elaborated set of documentation means built in into Scrum. Epics, user stories, source code, acceptance tests, prototypes, a technical environment support the design, implementation, build, test and deploy cycle with versioning and release management (at least hopefully \u2013 if not, well you know now where you have aspects to improve. To be straight \u2013 this is where we at digitec Galaxus as well do have room for improvement).<\/p>\n

Subject matter experts (example: actuaries in reinsurances), technical experts (example: hearing experts in the development of hearing devices) all have very special tools and environments. Actuaries often use Excel. I have seen monstrous solutions built from man dependent Excel workbooks driving business critical risk management solutions implemented by actuaries in reinsurances. Nobody else except the creator understood these complicate solutions. I once had the job to migrate such a solution into a scaling Java solution \u2013 what a nightmare. The most important individuals in this project were Prolbares (see above) that translated the requirements of the actuaries, hidden in the Excel beast, into something executive managers (\u201cwhy is it so expensive to rewrite an Excel worksheet in Java??!!\u201d) and SW engineers (\u201cas a reinsurance key accountant I want to \u2026\u201d) understood.<\/p>\n

Point is: Between SW engineers and experts (and managers) there is a distance that Prolbares try to reduce or even to eliminate – with distance defined as well as physical distance as mindset distance. In true agile environments elimination is the aspired state. What is important in respect of documentation: SW engineers and experts both have their specific way to deal with documentation.<\/p>\n

With this requirements of SW engineers and experts for documentation are:<\/p>\n