{"id":5572,"date":"2016-08-03T17:02:48","date_gmt":"2016-08-03T20:02:48","guid":{"rendered":"http:\/\/blog.plataformatec.com.br\/?p=5572"},"modified":"2018-09-24T11:51:50","modified_gmt":"2018-09-24T14:51:50","slug":"5-strategies-to-improve-software-development-workflow","status":"publish","type":"post","link":"https:\/\/blog.plataformatec.com.br\/2016\/08\/5-strategies-to-improve-software-development-workflow\/","title":{"rendered":"5 Strategies to improve software development workflow"},"content":{"rendered":"

It is difficult to come up with a plan when you find yourself in a dysfunctional environment. Everything is on fire and there is no time available. Tight deadlines, pressure, working overtime, unsatisfied customers, waste, and a whole lot of other chaotic stuff that piles up and makes it difficult to pick the most critical problem to fix.<\/p>\n

I will offer guidance in situations like this with five strategies in a recommended sequence. They are aligned with Lean principles and will work as a guide whichever method you use, be it Scrum, Kanban, XP or any other.<\/p>\n

These strategies came to my attention while attending a course called SoftwareZen<\/a>, by Alisson Vale. Alisson is a Kanban pioneer here in Brazil and I strongly recommend his course to all Portuguese speakers out there.<\/p>\n

The strategies were complemented with our experience at Plataformatec and the content I presented (here the slides in Portuguese<\/a>) at Agile Floripa 2016<\/a>.<\/p>\n

An overview of the strategies<\/h2>\n

A work system, like any other system, has an input, a processing area, an output and a feedback loop:<\/p>\n

\"Agile<\/p>\n

To be generic, let’s call “work items” all things that flow in a working system. The processing area deals with work items related to the present, the system’s input has work items that will be processed in the future and the output has items that had already been worked on.<\/p>\n

It’s a good practice to start improvement by looking at the “Present”. This will give good leverage to the actions applied. It doesn’t mean that “Future” and “Past” are not important, they are complementary. Learning with “Past” work items can make your “Future” ones better.<\/p>\n

Having this in mind, this is how the strategies are related to the system areas and the recommended sequence to apply them:<\/p>\n

\"Strategies<\/p>\n

In the following weeks, I’ll post the first two strategies, “Start with work in progress” and “Reduce work item size” as a preview of an ebook I’m writing, 5 Strategies to improve software development workflow. The e-book will feature the content below:<\/p>\n