Archive
Att börja jobba som juniorkonsult
Tänkte dela med mig av mina erfarenheter från första halvåret som juniorkonsult samt komma med tips till alla som står och gläntar på dörren till yrkeslivet. Efter att ha studerat datorspelsutveckling på DSV samt läst en del fristående kurser kände jag att det var dags att ge mig ut i arbetslivet. Efter 4 år av universitetsstudier började jag därför i Kentors java-team hösten 2013. Omställningen från det akademiska till yrkeslivet var minst sagt chockerande till en början. Tempot upplevde jag som mycket högre och jag fick verkligen anstränga mig i början för att ta in allt nytt.
En ny Kentorblogg har fötts!
Nu har även Lars Wennerholm, Seniorprojektledare på Kentor, börjat skriva en blogg. Lars har många års erfarenhet av projektledning och krav i IT branschen, och vi lär nog ha många intressanta inlägg att se fram emot framöver!
Stop Using Story Points
I recently read this incredibly interesting post from Industrial Logic by Joshua Kerievsky about his experiences with using story points in the agile development process. I have personally always been a bit wary of story points, since in the end, they just seem to get translated back into hours anyway. I have been witness to this several times, both as a developer and a Scrum Master. When you ask people to estimate in story points, preferably with the standard definition of 1 story point equals one day of productive work, then you invariably get estimates that when you multiply them by 8 are the same as they would have been if you had estimated in hours in the first place. Read more…
Making the Daily Standup Work
Interesting piece on Jeff Sutherland’s blog about making the Daily Scrum work when there are a lot of people with varying schedules involved in the project. In particular, he uses the example of using Scrum in Church, which I admit, is something I never would have thought of. Making the Daily Standup Work.
Testing and the Definition of Done
Previously, I have written about my current project, a system used by Stockholm Country Council for computing compensation from the county to the various health care providers within the county for services provided to the people of Stockholm. I have also mentioned previously that I have taken the role of de facto Scrum Master. In addition, I have become the de facto test manager in the team. The system does not really have users per se, but rather, it takes input in the form of XML files, it makes a bunch of calculations on this data and then it spits out some new XML files. Read more…
Combining Scrum and Waterfall
Interesting post on combining Scrum and Waterfall
A very interesting article about combining Scrum with the Waterfall method (an organizational constraint in this case) and what impact this has on testing.
Certified Scrum Master
I have spent the last two days taking Crisp’s Certified Scrum Master course, and I am so pleased that I decided to do so. I have “sort of” doing Scrum for the last several years. Sure, we have been working with backlogs and sprints, we do sprint planning and try to include the product owner, and we occasionally do a retrospective. We have a Scrum board and we move things across it from Backlog to in progress to done. Read more…
One Month In
One month ago, I wrote this short post about how the Java Team at Kentor was about to officially take over the management and continued development of one of the most important health care billing systems in Stockholm County. Now we have been at it for a month, and things have gone relatively smoothly, with the occasional incident and one considerable change in project organisation. Read more…
Continous Delivery
I recently read this article about Continuous Delivery and I started to reflect about what continuous delivery and continuous integration are all about, especially in relation to the projects in which I have been involved. A large portion of my early career (off and on from 2003 until 2010) was spent developing a Learning Management System with more than 100,000 users worldwide for a large company in Sweden. In that development process, there were very clear lines between the supplier’s development team (where I worked) and the customer’s operations team, which was responsible for the entire mainframe environment on which the system was deployed. Read more…
Planning Poker
I wrote a short post the other day about a recent Scrum sprint planning meeting that I led and about how much I liked using Planning Poker. As I mentioned in the post, I think Planning Poker is a great tool for engaging the less experienced developers in a group, giving them a chance to make their concerns about how software should and will be developed heard.
I stumbled across this post from Javalobby this morning, which basically talks about the same thing. Even better, it has a great Dilbert cartoon to illustrate its point. Everything becomes clearer with Dilbert.
