SAFe Framework for Agile, mostly unnecessary
Bottom Line: IMO SAFe is a mostly Waterfall, Bureaucratic and untrue implementation of Agile. Agile is simply the construction of cross functional technical teams with a Business Owner inside. It is not difficult to assemble
Key reasons why Agile for Cloud deployments may fail
Using Agile within Cloud deployments can fail for the following key reasons: Culture of the firm is not democratized and does not allow for experimentation, failure, or subject matter expert control over technology components. The
Why Agile is Superior to the Bureaucratic Mess called ‘Waterfall’
Waterfall theologies are directly responsible for the failure of ~70% of IT projects of any size and variety. Forrester estimates that 68% of projects fail due to poor requirements gathering; Gartner regularly publishes reports outlining
Agile in reality
What is Agile? About 70% of projects fail. Most of these – a vast majority – still use the Waterfall methodology. Waterfall is completely unsuited to building software, code, systems or complexity of any variety.
When to use Agile and some challenges
When should firms use Agile? The short answer is that within IT, it should be the de-facto methodology for development, migration and delivery of IT projects. However, Agile is difficult, mandates a long-term investment along
Agile Centre of Excellence (COE)
Within VLE’s (very large enterprises), the culture of silo’s is difficult to fracture and re-arrange. Waterfall or traditional methods of IT management and deployment do not easily surrender or die-off. There is always a rear-guard
Agile & Scrum: A comprehensive review, benefits, key success factors
Strengths and Best Practices Agile-Scrum’s strengths include adaptability, flexibility, improved team structures, and an ability to incorporate changing requirements, leading to improved quality, and Business-IT collaboration (Inayat et al 2014). Chandrasekara (2017) and other case
What is Architecture and how can Agile improve Architectural Design?
A curious aspect of IT Architecture is that there is no single definition of Architecture. This causes real problems on projects. The reason is that Architecture and Design, are the pre-requisites for good IT systems.
Agile and Domain Driven Design
Issues with Agile include scaling and not having a detailed design which considers all aspects of security, interoperability and networking. OOAD and Domain Driven Design can help alleviate these issues. Agile Agile is not only a delivery