The idea behind the Praqma blue prints wiki is that we present all the good ideas and requests we get from various sources and turn them into concrete design stories in the format of Blue Prints and hereby make them available for students and interns who are encouraged to engage and contribute to the implementations.

Open Source
All of our blue prints are related to work that needs to be done in Open Source Software (OSS), so just to get things straight; All implementations of our blue prints will be Open Source - no matter who provides the labor. That does not mean that these project don't carry business opportunities. Praqma itself is a living proof of that. But especially as a student this is a great advantage. It means that you will actually be delivering and releasing you running code and your contributions will be judged by the toughest jury you could possibly meet; Your peers in the community.

Praqma as product owner and technological supervisor
Praqma offers to supervise and help setup - or even host - the infra structure required to enable the development. We will normally attach two Praqmas to the implementation of a blue print. One will take on the role as product owner the other will be a technology supervisor. We will take time to meet you at the end of each sprint (typically here in Praqma Plex every fourth-night). On these sprint meetings we will:

  • See a demo of your runnig code
  • Evaluate the sprint
  • Pull items from the backlog to form a new sprintlog
  • Which you will estimate and commit to

...and then we see you again in 14 days.

In between sprint meetings you are welcome - even encouraged - to make contact with your appointed technology supervisor, to discuss issues and get help to blow up road blocks - or learn how to get pass them by secretly hidden trails.

We might also be interested in hosting your entire group here at Praqma Plex, with desks, lunch and professional supervision and mentoring for a certain amount of time during an internship. Since Praqma was founded in 2007 we have hosted 5 interships.

Workloads and estimates
Our blue prints are estimated to have workloads that spans from a few hundred hours to never-ending-stories. We have put our rough estimates on each single description. But we use an agile approach and we count working software as the primary measure of progress. So talk to us; We can help you scope the blue print, so that parts of it can fit into the exact time span you have available.

Continuous Delivery
We see continuous delivery (CD) as a practical instantiation of the agile development principles. So be prepared, that if you take on the challenge to implement one of our blue prints, we will expect you to implement a CD tool chain as well. As a minimum it shall contain:

  • Use of a Distributed VCS with integration to a change management system
  • Unit tests (UT)
  • Code coverage on UT must be higher than 70%
  • Static code analysis (style check)
  • Automated deployment
  • Automated functional tests

...and if you find these disciplines to be unnecessary and tedious work we dare you; "You will not be able to earn fame and recognition in the OSS community ...without it"

NOW GO! our wiki and see what we have for you - and know this: The real world is always a few steps ahead, we might have more blue prints on our backlog, which just aren't published yet. Make contact, ask us!

Project info
6. Marts 2014
Contact info
Lars Kruse