WikIT42 - Structure for IT Division and IT Products

After introducing Confluence three times in three different companies I made a template which consists the best practices of how you could structure your IT Division and IT Products within your organisation. Although the three different companies have completely different domains (marketing, payment and environmental services) the stucture of the division and products are quite the same. So if you need to introduce Confluence in your company and you would like to bring the "product team" together, just take a look at WikIT42: http://bit.ly/wikit42en

A German version can be found here: http://bit.ly/wikit42de

For discussion I open a Gitter chat at: https://gitter.im/wikit42

Enjoy,
Lofi

Comments

Software Development Macro and Micro Process

If you think that in year 2012 all companies which produce software and IT divisions in our world have already their optimized software development process, you are wrong. It seems that we - software architects, software developers or whatever your title is - still need to optimize the software development process in many software companies and IT divisions. So what do you do if you enter a software company or IT division and you see following things: 1. There is a perfect project management process to handle all those development of software but it is a pure project management without a context to software development. So basically you only take care of cost, time, budget and quality factors. In the software development you still use the old fashioned waterfall process. 2. From the tooling point of view: you have a project management planning and controlling tool but you are still in the beginning of Wiki (almost no collaboration tool) and you don't use issues tracking sy...

Why "Polyglot Programming" or "Do It Yourself Programming Languages" or "Language Oriented Programming" sucks?

Last year we saw the launch of a new Web programming language Dart - Structured Web Programming from Google. A very interesting approach to support web application development. Not so long after Go, Groovy, Ruby, Scala, << name your DSL here >> ; we see Dart. Is it a good thing to have at least one programming language to solve one problem? The answer is, like we already know, it depends. Some important backgrounds you should know about the multi programming language paradigm are following: 1. You can read Martin Fowler article about language oriented programming with language workbenches which enables you to write small programming languages easily. In this article I see everyone writing their small languages, everywhere. In this concept we see DSL (Domain Specific Language) as the future of our programming activities. Source: http://martinfowler.com/articles/languageWorkbench.html 2. Neal Ford talked about Polyglot Programming, combining multiple programming language...

GWT Training for Java Developers with GWT Boot

I'm always a fan of " one language solution with Java to rule them all ", here are sofar my opinions about Polyglot Programming: Why "Polyglot Programming" or "Do It Yourself Programming Languages" or "Language Oriented Programming" sucks? Warum Polyglot Programming nicht praxistauglich ist Java als universelle Programmiersprache Until today nobody can excite me about Polyglot Programming. My points are getting another big support after I read the " Rise of Polyglot at Netflix " presentation which says that Polyglot is expensive , also for company in the category of Netflix. At the end of the day we need to be productive . Our applications should have a high quality standard and the total costs (TCO) of our software development should be manageable and low . To be able to reach this goal we have Java with Spring Boot or JakartaEE on the server-side which offers REST interfaces. So logically for user interface development ...

Lofi model @ work

Search This Blog