Our software engineering blog is now open !

Our software engineering blog is now open !

Announcements
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] We are proud to open our own blog about software engineering. It will be an opportunity to discuss methodologies like Scrum and Devops, as well as technical matters or even strategic aspects. [siteorigin_widget class="SiteOrigin_Widget_Image_Widget"][/siteorigin_widget] Our team composed of senior developers, agile experts, product owners and devops coach will propose articles on various topics of software crafting that thay work with on a daily basis. Here are some articles that you may like: [siteorigin_widget class="SiteOrigin_Widget_Features_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget]
Read More
Scrum hoax #1: Scrum prevents transparency

Scrum hoax #1: Scrum prevents transparency

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] Better transparency is one of the key value proposition of Scrum and one of its pillar. Several parts of the framework are designed to help it and make sure to keep stakeholders aware of the progress. More often than not, this does not work as expected and Scrum is blamed for that. It is a perfect opportunity to open this series of articles around the Scrum hoaxes. In today‚Äôs article we will discuss the black box syndrome some organizations encounter while implementing Scrum, and cover the possible causes and solutions. [siteorigin_widget class="WP_Widget_Media_Image"][/siteorigin_widget] Some times ago, I had a discussion with a senior product analyst about how Scrum impacted its organization. Like some people complaining here and there, he was not happy at all with the methodology. Bottom…
Read More
A branching strategy for Scrum using Git

A branching strategy for Scrum using Git

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] Scrum is a great framework. If you do not know it, you should check it out and then come back here ! Defining a branching strategy suitable for Scrum is not so simple, here is a proposal. Scrum is designed to develop product among iterations (called sprints). The sprint backlog contains stories which represents the work to do in the scope of the sprint. At the end of the sprint the Product Owner will decide if the proposed product increment is accepted or not. It is common for Scrum teams to have strong difficulties with the branching strategy to apply to the product they are building. As a matter of fact, the expected level of collaboration on each story, the need to propose a shippable product increment,…
Read More