subshell News & Blog » Agile
Latest news on our growing client base and latest wins. Plus: Stories, tips and tricks from the team at subshell.
The Sprint Process At A Glance
Scrumclipse: An Eclipse IDE Plug-In To Follow The Sprint Process
Like described in a previous article subshell organizes its software development with the agile methodology of scrum. Of course we have a big scrum board with DIN A5 cards for each task and a burndown chart to illustrate the process of the sprint. Thereby each task has a corresponding issue in our JIRA bug and issue tracking system and the whole life cycle of the tasks is managed there:
- The issues are assigned to the developer who currently works on it.
- The estimate and the spent time is logged in the working log.
- The state of the issues (e.g. "In Progress", "Review", "Test", "Done") is switched in JIRA.
- And so on...
- Finally the burndown chart is calculated out of the working logs automatically.
In addition to the "traditional" scrum board and burndown chart we created an Eclipse IDE plug-in that integrates the scrum board, the burndown chart and a sprint statistic into the developer's IDE.
Die Bugspringflut vor dem Livegang
...oder wie man mit Fehlern umgeht, die erst kurz vor dem Relaunch auffallen.
Ich bin viel unterwegs. Berate hier, gebe Schulungen da oder leite ein Projekt wieder woanders. Ich habe somit oft Einblick in die Arbeit anderer Scrum Teams. Man trifft auf tolle bunte Scrumboards, unterschiedliche „Definition of Done“- Aushänge und eine sehr unterschiedliche Art und Weise Scrum zu verstehen. Vor allem der agile Ansatz gerät in vielen Fällen an der einen oder anderen Stelle unter die Räder. Einen davon habe ich mir heute ausgesucht: Die Bewältigung der Bugflut vor einem Relaunch.
Using Scrum at subshell
This post is about how we at subshell organize our software development using the agile methodology “Scrum” and how we adjust our interpretation of Scrum to our own requirements. After 80 sprints, Scrum meanwhile structures working life at subshell into two-week-sprints. One sprint starts with a Sprint Planning Meeting and ends with a review and a retrospective.
Automatic Calculation and Visualization of Burndown Charts
We manage our software development with the agile methodology scrum. As usual in scrum we use a Burndown Chart to visualize our sprint progress. For a couple of years we calculated the daily values for this chart manually. But recently we discovered a possibility to automate this task. This article describes how we reached this goal, through the power of JIRA, Groovy, Google Spreadsheet and Google Chart Tools. But first of all I will briefly explain our workflow for each ticket or in scrum terminology for each user story.
Categories
Sophora CMS - A New Take on Content Management
Sophora is optimized to meet the needs of modern companies that produce up-to-date multimedia content on a large scale and that require fast delivery of their content.
Toromiro
Toromiro is a professional tool for the administration and editing of Java Content Repositories (JCR). JCR is powering some of today’s most successful solutions for content management and digital asset management.