One of the software project risks is “Correct resource allocation at the correct time is a crucial key to project success”. That is so true and happens all the times in the projects where project managers want tasks finished quickly… Continue Reading
Incomplete requirements can impact the schedule of the project and delay it. That is why requirements validation is essential. The agile approach is beneficial as requirements are validated at the end of every iteration as the end user gets a… Continue Reading
Design patterns may not be suitable for complex projects. We have in-depth discussed during coursework how to manage complex and critical systems better. “Especially, the cost can be a huge problem when applied to the complex system.” The statement above… Continue Reading
I believe it is only with experience that you learn if applying a design pattern would be beneficial or not. And at what stage it should be considered. For instance, if writing a piece of code, you can see which pattern… Continue Reading
“When the team is not familiar with a design pattern, and the timeline of the project is limited, it will not be the best choice to lose the time over introducing a difficult design pattern”. The above statement by a peer caught my attention. When doing the… Continue Reading
An interesting discussion: whether agile methods are best suited for critical systems or not? The lack of formal documentation of agile methods is a drawback. I too believe in the absence of upfront planning and formal documentation is important to… Continue Reading
The example of the Universal Credit is a good example of misunderstanding agile methods. Similarly, USA’s Health and Human Services spent $174 million and ended up with the decades most public software failure Healthcare.gov. This project used agile method for… Continue Reading
I think Scrum and Kanban together are even better. Scrum is the most systematic Agile method, which ensures a foreseeable, strategically planned and an iterative product outcome. It meets up greatly with the changing requirements. Also, the roles and responsibilities are precisely defined using Scrum. Whereas, Kanban is less… Continue Reading
“A scenario where Agile would have a positive impact is the development of a competing product of Microsoft Word” The example mentioned above caught my attention. It reminds me how Spotify stays successful by using agile methods. Since its inception, Spotify has imbibed agile… Continue Reading
It is hard to scale Agile for large-scale project probably because Agile methods were originally designed for small and single-team projects (Boehm and Turner, 2005). With the increase in the size of an organization, the difficulty of introducing agile methodology increases (Dybå and Dingsøyr, 2008). One main… Continue Reading