References

Cervone HF Understanding agile project management methods using scrum (2011)

J Highssmith Agile software development, boston, MA, USA: addison- WESLEY longman publishing CO, (2002)

K Beck, Extreme Programming Explained : Embrace change, reading, mass (1999)

K Schwaber and J Sutherland The scrum guide  scrum.org (2010)

M.Cohn, Succeeding with agile software development using scrum, Addison-Wesley (2009)

J Tabaka Ways agile adoption fails.f stricky minds.com Column stickyMinds.com.retrieved March 2011

Abrahamsson,p, salo, Pontainies J & waista J (2011)

Lowell & Ron J (2004) Extreme Programming and agile software development methodologies

7. Conclusion

 Conclusion

This assignment blog was about the explanation of the scrum framework and the features , the scrum team roles and scrum methods. The arguments for and against the adoption of scrum was explained. The benefit and no benefits of scrum agile development methodology was also explained for the scrum methodology. The two aspects of agile methodology was also considered

6. Two aspects of agile methodologies

 Two aspects of agile methodologies

XP

XP- is the software development methodology that's part of what's collectively known as agile methodologies. XP also called extreme programming. Extreme programming is an agile software development framework that design to produce  higher quality software and higher quality of life for the development team. Extreme programming is a good idea because is the most specific of the agile frameworks concerning appropriate engineering practices for software development and it considered as important one. The extreme programming method object to establish frequent product releases within shorter development cycles. The main aim is to enhance productivity and to create more checkpoints that allows adapting frequent changes in customer requirements. Extreme programming produce a high quality product in a short period of time. XP has some common goals which are improve the productivity, develop the path to improve the process and develop the own style for development activities. There are six phases that are in an agile XP methods which is planning, analysis, design, execution, wrapping, and closure (K Berk,1999).

SCRUM

scrum is a frame work for effective collaboration among teams working o complex products. Scrum consists of meetings, roles ad tools to help teams working o complex projects collaborate and better structure and manage their workload. Scrum is an agile development methodology used in the development of software. The roles on the scrum is that teams focuses on building quality software. The owner of a scrum project focuses on defining what are the characteristics that the product owner and development team. The scrum has this goals helps the scrum team focus, drives collaboration within the scrum team, helps with prioritisation during the sprint and guides feedback from stakeholders. The scrum teams turns a selection of work into an increment of value during a sprints(k schwaber, 2010)

5. Benefit and non benefit of scrum agile development methodology

 Benefit of scrum agile development methodology

Benefits

Scrum can assist team the team to complete the project creation quickly and efficiently. Scrum ensures effective use of time and money. Development projects are divided into easy controllable sprints. Development are coded and tested during the sprit reviews. Work adequately for quick moving development projects. The teams gets clear visibility through scrum meetings. Scrum being agile take up the feedback from the customers and stakeholders. Short sprint enables changes based on feedback more easily. The individual effort of each team members is visible during daily scrum meeting.

Non-benefits

Due to the lack of definite end date scrum often leads to scope creep. The possibility of project failure are high if individuals aren't very committed or cooperative. Adapting the scrum framework in a large teams is very difficult. The frame work can be successful only when team member has a knowledge. Daily meetings sometimes frustrate team members. If any team member leaves in the middle of the project it can have big negative impact on the project. Quality is hard to implement until the team goes through an aggressive testing process (J Highssmith, 2002)

4.Arguments for and against the adoption of scrum

 SCRUM

Scrum is one of the framework under agile development methodology. It is a lightweight process widely used for complex projects and breaks the process into cycles called sprint. Scrum adoption process started while every member of the team is engaged in his/her everyday tasks. Daily scrum meeting add extra pressure to the scrum team member, they have to work hard  They used to meet weekly and later twice a month. As teams started to skip daily meetings it also affect the learning process of scrum between the team members (J Tabaka March 2011).

The production owners were recently appointed which lead to product backlog consisting of user stories that are different levels of abstraction and inconsistent with the previous versions of the software. The team in the initial estimation of existing projects. Project managers and many members of the agile method. The sprint review meeting was designed to support organisation learning due to the fact that each scrum master had his own view of what is scrum. Due to the fact that each scrum the learning has become non existent (M.Cohn 2009)

3.Scrum Framework

 Scrum Framework 

The Durban University of Technology needs to develop the internal and contracted system development. The programmer should use the scrum framework for developing the software. Scrum framework is based on set of values, principles and practices that provide the foundation  to which an organisation will add its unique implementation of relevant engineering practices and specific approaches for realizing the scrum practices. The scrum framework consists of scrum team their associated roles, ceremonies, artifacts and rule which help the team to work together. This scrum practices would be the key structural components for development and contracted system development. Scrum framework has a lot of features and specification. The product owner defines a vision using information from stakeholders and users. . They classify and define pieces of value that can be delivered  to move closer towards the product goal. The product owner have to order the backlog before the developers can start to work to any piece of values. After that the teams will take the product backlog and arranges the requirement for committing the sprint  (cervone, 2011).

The stakeholders are for the project ad assigning the role of scrum master or another member of the team responsible for executing the plan. Teams creates a sprint backlog and plants its implementation. Construct the backlog for the project which comprises all elements the team must complete in order to finish the project and create plans for a sprint. Then they should be a scrum meeting. The scrum master should guide the team . During the meeting the team maintain an updated backlog, removing items and assigning out new items from the backlog as needed. Provide project updates, review  the work plans or concerns and deliver final product to stakeholders. After realising the product consider  organizing a project meeting with the team to analyse the performance of each individual sprint. The software will be finish and approve the deliver.

  SCRUM FRAMEWORK

Scrum roles

Product owner- creates product backlog and prioritizes the product backlog.

Scrum master- helps the team best use scrum to build the product and removes obstacles to progress.

Team- work together to achieve a shared goal and deliver values to users of their product or services.

Scrum  ceremonies

Sprint planning- establishes the sprint goal what can done and how can the work will be completed.

Sprint review- The entire scrum team inspects the sprints outcome with stakeholders and determines future adaptation stakeholders are invited to provide feedback on the increment.

Sprint retrospective -  The scrum team inspects how the last sprint went regarding individuals, interaction, processes, tools and definition of done

Daily scrum meeting- the developers inspect the progress toward the sprint goal and adapt the sprint backlog, adjusting the upcoming planned work.

Scrum Artifacts

Product backlog- An emergent, ordered list of what is needed to improve the product and the product goal.

Sprint backlog- The set of product backlog items selected for the sprint by the team members plus a plan for delivering the increment and realizing the sprint goal.

Burndown charts- graphical way of showing how much work is remaining in the sprint, typically in terms of task hours ,as the sprint progresses the amount of work remaining should steadily decrease and should tend toward being completed on the last day of the sprint.

2.Overview Of Agile Process

 Agile Process

Agile is a group of methodologies that shows a commitment to tight feedback cycles and continuous improvement. Agile is a kind of development methodology that anticipates the need for flexibility and applies a level of pragmatism to delivery of the finished product. Agile is the word which is used in different approaches for developing a software. Agile improves efficient throughout the organisation as the team work together and the team should understand their specific roles during the process or the project. Agile process is used to help the developing of the software. Agile methodology uses scrum process which keep on update and restore. There are different frameworks in agile methodology like scrum process, dynamic method, extreme programming, adaptive software development, feature driven development, kanban and behaviour driven development.

THE DIAGRAM BELOW ILLUSTRATE THE THE AGILE PROCESS

from image source Jordanjob.me/blog/scrum-diagram/

Agile software development also emphasizes on four core values which are individual and team interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation and the last is responding to change over following a plan. Agile methods strive to maximise the delivery of value to the customer and minimise the risk of building products that do not meet customers needs. Agile system development methods are intended to guide the projects in a volatile environment and suffering from the tenacity of every competitive market(cho, 2008)

1.Executive summary and Introduction

 Executive summary

Agile development is the approach to manage a project by breaking it up into several phases. It is the development of building the software in a sort period of time. Agile development it also known as software development that help teams to deliver value to their customer faster and easy. Agile design to provide better responsiveness to changing business needs and it also can concentrate on enabling teams to deliver workable increments. Agile is one of the simple and effective process to tur a vision for business needs into software solution. The blog is about a report. In this report there are benefits and non benefit of agile methodology for internal system development and contracted system development for Durban University Of Technology to build a software.

Introduction

In this assignment there will be an explanation of the scrum framework and arguments for and against the adoption of scrum. The sort of project that would benefit and what sort of project will not benefit it be also considered. The will be an explanation of the aspects of scrum in two methodologies which is XP(Extreme programming) and scrum. The benefit of the agile scrum process will be explain.