0

Allocation of project resources

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

0

Incomplete requirements delays a project!

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

5

Design patterns for complex systems?

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

0

Design Patterns

“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

0

Agile methods for critical systems?

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

0

Misunderstanding Agile Methods

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

0

Scrum and Kanban together

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

0

AGILE: Large scale Vs Small Scale projects

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