The document discusses common issues faced by German companies in software development projects. It notes that initial designs often cannot accommodate new requirements, and hidden cloud costs and inability to react fast enough to changing needs are problems. Many German firms struggle to communicate complexity to clients and lack a skilled workforce. Outdated workflows and lack of proper requirements understanding can cause issues. The document recommends hiring independent contractors, establishing strong feedback loops, separating agile and Kanban workflows, implementing automated testing, and constantly evaluating market and client needs. It warns that outdated software practices can lead to high costs, unstable code, risk of failure and security issues, difficulty finding skilled workers, software deprecation, and potential legal problems.

1. www.javaprofide.de

2. • Software development and quality assurance.
• Helping clients to understand the requirements
of theirs project or project's.
• Creating real and honest estimates and solution plans
for the implementation of client requirements.
• Offering training and workshops in various IT technologies.
• 3D design
• Unity3D game development.

3. The presented information
based on ca. 5000 interviews
with German companies!
This is not book knowledge!

5. The initial design does not work with new requirements

6. Hidden cost‘s of running production apps in cloud.

7. Regional time difference and inability to react fast enough to
change of requirements

8. Many German companies working with big clients unable to
communicate the complexity of development and or luck of
workforce

9. Way to many German companies rely on manual testing and
common practices established in last 10 years!

10. Many German companies rely on established and „time
verfied“ outdated und really inefficient workflows

11. Software development is not a car production line!

12. Software development is not a car production line!
Luck of proper requirements and understanding what market
and client really needs

14. • Hire external and vendor independent IT contractors.
• Make a goal to create realistic implementation plans and execute them!
• Initiate strong feedback loops from your IT departments , 2 weeks iterations!
• Don‘t mix agile workflow together Kanban vs Scrum !
• Establish culture of testing your software through automation!
• In case of different regions and developers communication ,
make sure that they can work independent from each other!
• Understand hiring new developers wont speed up project!
• Evaluate on constant base the market and your client requirements
for the final product, manage theys expectations.
• Provide clear understanding on what your really expect from your team.

15. 1. High cost of adding any new features into your software!
2. More unstable codebase , probability of high failure and data loss and
possible issues with security.
3. Luck of risk mitigation , which will definitely will result in complete
financial failure of your company!
4. Difficulties in finding skilled workers for your current software projects,
due to very complex software stack and general overhead of workflow
5. Deprecation of the software , after 10 or more years of investment!
6. Potential breakage of the production pipeline and as result problems
with logitstics of your company
7. High probability of legal problem , due to inability to respond fast
enough against any software related issues!

16. www.javaprofide.de
www.ocgforum.javaprofide.de