Question

Why are agile methodologies generally not suitable for hardware-based projects as opposed to software projects?

Answer 1

Why are agile methodologies generally not suitable for hardware-based projects as opposed to software projects?

Agile Methodologies are the creativity incorporated with principles ,but hardware based projects on well defined structured steps ,it is not completely creativity ,it completely based on the well defined theory.

An Agile process is one that incorporates the principles of the Manifesto for Agile Software Development, which states We are uncovering better ways of developing software by doing it and helping others do it. The Oxford Dictionary defines the word “agile” as “Able to move quickly and easily.” For present purposes, a simplified description will suffice for this paper: Agile processes are designed to produce planned deliverables quickly, while adapting well to uncertainty and unexpected changes. Through this work we have come to value, Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan. Many Agile software-development frameworks or processes have been defined, Some of them ,such as Dynamic Systems Development Method (DSDM), and Feature Driven Development (FDD) are well-defined but are not widely used. Over time, the Agile processes for software development that have become dominant are Scrum and Kanban.

Agile refers to an iterative way of developing. It was created to brainstorm an ideal development process. Their manifesto respects and acknowledges best practices like normal due diligence, documentation, contracts, and plans. However, it's main focus is on things like working product, collaboration, and adaptability to get things done. It is a direct response to process-centric methods that are documented to the tiniest detail. Agile is the anti-'Dilbert.' The engineers who founded Agile wanted something that allowed creativity and most of all, something that helped them build successful products, which was proving harder and harder with traditional, top-down processes. There is one problem, though. This is all a general guideline that allowed for many different Agile methodologies.

Before jumping into an analysis of the applicability of agile in hardware development, it is important to first categorize developing hardware as either a creative or defined process. Presumably, hardware development as a creative process would be similarly crippled by traditional project management practices and similarly benefit through the application of agile development. If, on the other hand, one decides hardware development can truly be captured as a defined process in an accurate and reliable project plan, there is little point in going further because the problems agile is designed to address simply do not exist.

There are several questions that can help characterize hardware development as either a creative or defined process.

· Is it possible to build a detailed project plan that accurately captures a complete development cycle prior to development?

· Do detailed project plans remain stable over time?

· Is it possible to build a concise set of product requirements that will satisfy customer and market need in the future?

· Do product requirements remain stable over time?

· Are products consistently delivered on schedule?

· Do products consistently meet market demand and customer need?

· Are target technologies thoroughly understood and unlikely to change?

· Would a hardware team design and build a product the same way twice?

· Are product architectures likely to remain stable over time?

· Are people and their respective skill-sets interchangeable?