Tag Archives: Scrum training

Pentalog’s agility program: 2014 achievements and perspectives


As you might have read on our blog, “Guépard” is the name of Pentalog’s agility program that started in July 2014. I’m pretty much sure that everybody is curious to find out what Guépard offered us last year.

This transition process focused on 4 dimensions:

  • Trainings
  • Coaching
  • Knowledge sharing and camps organized by Pentalog Institute
  • Alignment of internal processes


In 2014, the Agile, Scrum and Kanban trainings represented an important part of the program. How did they help us? Thanks to them, we were able to align with the Agile objectives, values and thinking. Moreover, we learned together how to better use the Scrum and Kanban frameworks to reach our goals.

For the entire period of the program, we designed a plan for almost 1500 training man days on topics

Read more « Pentalog’s agility program: 2014 achievements and perspectives »
Tagged: , , , , , , , | 1 Comment

Critical checkpoints in Scrum – Part 1 – Release Planning

Two months ago, I was doing an agile practices review for one of our clients and I was surprised to see that despite his willingness to practice Scrum there was little understanding of it. Even if most of the people I’ve met in the agile community, experienced at least the Scrum certified course, I can see during debates that there is a major gap between how they perceive it and genuine Scrum. It is useless to remind that the lack of comprehension might do more harm to the organization than before the ScrumBut, as described in my previous article Scrum requires a different mindset.

Suddenly all the important stuff we’ve been used to from the beginning of times disappeared and a strange mixture between the defined process control model (old approach) and the empirical

Read more « Critical checkpoints in Scrum – Part 1 – Release Planning »
Tagged: , , , , , , , , , , , , , , , , , , , , , , | 1 Comment

Scrum requires a different mindset

“I had difficulties respecting deadlines and products were flooded with defects and bugs, which made it even more difficult when accepting changes required by the customer until I decided we have to step into agile world! In Scrum they accept changes diminishing impact because there is no document to update. The team is self-organizing and more responsible so we will have fewer defects in the end. Traditional development models are no longer sufficient or effective.
6 months after software manufacturing with Scrum, we understood that all this was just good advertising and worst results were just about to come!”

Does this desperate message sound familiar? Yes, too familiar! As a CTO at Pentalog I had the opportunity to meet potential clients with similar problems: “we’ve done Scrum but it doesn’t work for us, so we

Read more « Scrum requires a different mindset »
Tagged: , , , , , , , , , , , , , , , , | 8 Comments