Lean Software Development and Enhancing Software Development Projects

Agile is an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework, with "just enough" ceremony, that produces high quality solutions, in a cost effective and timely manner which meets the changing needs of its stakeholders [1].

Lean Construction has different sets of principles, tools and techniques that is applied to construction which lead to reduction in waste.

Capability Maturity Model (CMM) is used when we talk about or refers a proper process improvement approach which contain process models. It was developed by the Software Engineering Institute (SEI). This paper contains a background discussion of CMM. An overview of the development by using CMM Technique, concluded summary of the models, and a proper description of the software development process improvement models and the outcomes given by the software suppliers; this comparison can helps us to understand the usage of CMM or CMMI, its approach to process improvement; summarizes some of the strengths and weaknesses of the CMM; it tells the current status of the practice and how much money you can save by investing on software process improvement; the comparative study of the Capability Maturity Model which shelters the using of capability maturity model, key process areas, structure of capability maturity model, staged representation, behaviour at five different characteristics , stages, assistances, profit and difference between CMMI and CMM.

Mr Taichi Ohno first developed the Lean Concepts at Toyota ( Womack, 1998) The principles he developed are applicable both to the manufacturing and the service sectors( A.Lakshminarasimha,2005). To enable a proper perspective on the concepts of Lean, an attempt is made to briefly recapitulate on them.

Programming advancement is a lavish, and regularly a troublesome methodology. It is all around recorded that product activities are ordinarily over timetable, over spending plan and regularly don 't meet client prerequisites. The fundamental issues are all connected with individual’s related issues. To address this issue, the Agile theory was presented in the mid 90 's with a related arrangement of Agile routines. These techniques are particularly intended to enhance programming venture group administration. Readiness in short intends to strip away however much of the largeness, generally connected with conventional programming advancement techniques, as could be expected, so as to elevate speedy reaction to evolving situations, changes in client prerequisites, quicken venture due dates, thus on [1].

Agile movement gives alternatives to the normal way of project management. The Agile way is usually used in software development to assist businesses to react to the unpredictability.

The core objection behind lean systems is to maximize customer value while minimizing waste. Basically, lean is defined by using fewer resources in order to make a perfect value for customers. How lean systems work, they use a highly skilled workforce and flexible equipment in order to make some advantages. Such as mass production which is the high volume and low unit cost. And craft production which is the variety and flexibility, this will help eliminate waste for the producer and consumer. Luckily, this approach has drawn attention to other services. For example, lean systems aren’t only suitable for manufactures but also health cares, offices and shipping and delivery. The misconception that lean is a tactic or cost reduction program is not necessarily true, but it is a process of thinking and acting for the entire company. In order to accomplish lean system thinking changes must refrain from management optimize separate technologies, assets and vertical departments.

Today’s world market is much faster. Every industry is now become the result orientated. They need results in quick time. Like any other industry IT industries also force to make the changes in concepts and techniques they were using traditionally. The traditional models like waterfall, Incremental model, RAID model are not useful for most of the current project requirement. Nowadays project requirements depend on many other unstable concepts, which make the project less predictable. Because of these entire unpredictable project, agile becomes the first choice of most of the clients. The agile software development methods are more adaptive approach, while conventional/traditional software development methods are predictive approach. In traditional method all the project development plan is created before starting the actual development. Once the designing is completed we can’t make changes. On the other hand an agile methodology has the provision to acquire such changes even after the coding is started. Agile relies more on the incremental, iterative development cycles. Agile methodology software is developed in the small periods. Agile is for the projects whose requirements are not fully discovered, projects where output is not predictable. This makes the agile methodology more suitable for the current market situation.

The two case studies, provided by these respective authors, revolve around SMEs in two different countries. This paper will identify lean elements along with their motivations behind their lean implementations and identify the main differences and similarities between the two case studies in terms of general lean literature. Finally, a list of recommendations will be given to each case study and how their individual companies can improve the success of their lean adoption.

When developing a software product there are two different project management approaches that can be taken: waterfall or agile. Both waterfall and agile have their advantages and disadvantages but agile has become the more popular of the two, due to its ease of change during the devolvement process.

Ever since the Agile Manifesto came into existence in 2001, it has led many agile software development processes to spurt up. Dynamic Systems Development Method (DSDM), Extreme Programming (XP), Feature Driven Development (FDD), SCRUM and Crystal Methodologies are some of the most famous agile software development methodology famous today (Vlaanderen et. al, 20011), (Dingsøyr et. al, 2012). In the recent research done by (Dingsøyr et. al, 2012), it’s been found that XP and scrum are the two most common agile methodologies used currently. In their empirical research (Dingsøyr et. al, 2012) also found that most of the existing studies on agile methodology focus on XP and there are very limited studies done on SCRUM. The purpose of this literature review research is to analyze the existing research available on SCRUM methodology. This literature review will provide a broad overview on various information researchers are providing on agile software development methodology, keeping Scrum agile methodology in the focal point. In addition, this literature review will also address the advantages and disadvantages of SCRUM agile methodology. This research will help the audience to gaze over the recent study over scrum and will help in making the decision whether Scrum is the right agile methodology for their software development project.

The report begins with introducing the lean then presents the theories associated with it further elaborates on the principles, tools, processes and application.

The freedom that agile gives when new changes are needed to be implemented is very important. New changes can be implemented at very little cost because of the incremental releases. Even late changes in requirements are welcomed

n. Knowledge sharing and best practice based on real life lean implementation from other industries

Lean includes a set of tools and technologies for improving processes and services. The implement in an organization would be to develop methods that are both