CO665: Software Project Individual Report Introduction We as Team Volvic were delegated a task of creating a Transportation system of which we have managed to accomplish through lots of hard work and joint team collaboration. Our team consisted of 4 members, allowing us to split two members for the documentation and two members for the development of the software. Since, we had to implement the agile methodology, I chose the role of being the Scrum Master and documenter. The other team members were Ryan and Judy who took part in the coding, leaving Stone to help me with some parts of the documentation. Overall, we as a team have worked really well with one and other which mirrors in our end product. Personal Contribution Being a Scrum …show more content…
Having done this allowed us to create a foundation for our program. After having displayed all the visual elements, we started implementing the functionality for the traffic lights such as making them turn red, amber and green, besides this we also added functionality for the car to move across from one end to the other as well as stopping at specific coordinates. This allowed us to see if the car would travel on the set coordinates to the specific destination set. During this process, several IF statements were created to checking the traffic light status. After doing this, we added a detector which gave us reference points on our program enabling us to stop the car at specific locations. The strategy whilst developing the program was to break the code up into manageable chunks, so that it can be understood well. We carried out consistent testing to make sure that our code doesn’t have any fatal errors and bugs. If there was something we didn’t understand well we could ask our client Fernando for guidance or go to the Computing workshop. This helped us with the queries we had as well as to solute the problems with our code. Using the Agile approach enabled us to organize the software project into chorological order from the User Requirements to the End product. The requirements were formed by meeting our client Fernando on regular bases discussing the requirements of the program. He would assure
Agile processes do not devote much time up front to formal system specifications, but rather relies on continuous communication with the customer throughout the development process. The process accounts for the fact that needs often change or cannot be fully developed early on and is flexible to this. (+)
What makes Scrum different from other processes is the daily stand-up meeting referred to as "the Scrum" in which every team member should comment on the following three points (Krebs, J., 2005):
Cost and resource needs are higher for traditional than Agile due to Waterfall’s sequential development phase of all requirements determined in the beginning, software design and finally implementation of master design. The need for all information up front takes substantial time to gather and the sequential design does not allow for project changes as the flow enters into the programming stage. With Agile, costs remain low because there exists an incremental and iterative approach to the project, meaning less time is used to collect all requirements up front, the
The internet is the largest open market we have today. IwaL could easily advertise themselves on the internet to reach a larger than life market of customers. If IwaL were to use their Facebook page to advertise their products the amount of interested customers would be huge. Advertising online is also very cheap and in most cases free. With the right social media team IwaL could benefit from the internet greatly. Customers satisfied with their product would also be able to leave good reviews for everyone to see increasing their social capital.
Thus, Agile came into play. This is a faster and smaller method over traditional. Stakeholders get together with small teams to look at cost, resources and expected time frames. This team figures out the computer verbiage, checks and balances, verification coding, iterations, number limits, scripts, all in the early stages of development.
“Agile” was first introduced in 2001, by a team of software engineers looking to improve their adaptiveness and responsiveness to ever-changing requirements. Not knowing where to begin, the team began by formulating principles, which they would use to guide their new development process. Which, in turn, lead to the creation of the Agile Manifesto, and thus a new methodology was born.
Agile techniques should be used to solve the current issues faced by the company as agile techniques normally being used by the software industry help the business to act in response under the unpredictable situations faced. In Agile methodologies opportunities are been provided to evaluate whether the project is under the direction all through its development cycle. All this is being accomplished with the help of regular tempo kept in work, and the teams must show a product which is having the desired potential.
In order to achieve successful results within established time-frames and budgets, project managers are likely to employ methodologies models. A project methodology is a model that aids managers to plan, design and implement their project goals. Project methodologies are helpful to project manager in any field, for instance, Niel Nickolaisen CIO at the Western Governors University, is an advocate for the agile software development methodology. As these models grants flexibility when dealing with stipulations and scope changes on a project. Needless to say the agile software development methodology is just one example of a varied assortment of methodologies, each with their strengths and weakness. As such, it is up to the project manager to decide which methodology fits their needs, as there isn`t a one fits all solution.
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].
Agile methodology for a typical software project or any in environment in which the requirements are unknown or change quickly. Agile focus toward teamwork, constant user feedback, continuous improvement, face-to-face meetings, constant cooperation, early and continuous delivery of working
The agile methodology with scrum-based approach has worked effectively for our organization because it is flexible and iterative with continuous feedback and constant communication and favored by frequent and short delivery schedules (Chang, 2010). This approach brings about a high level of competence and high level of motivation to work. It also instills discipline and respect for time by
This report was compiled by a team of professional project managers and gives an objective insight to the project in full.
The traditional development method requires the definition and documentation of a stable set of requirements at the beginning of the project. It was inherited by other projects mainly related to construction which focused on the completion of one phase of production before moving on to the next phase, for example, laying the foundations of a building first and then proceeding with the further stages (Bowes 2014). Similarly, in Waterfall, the requirement gathering and designing work is done upfront before any coding takes place. The basic notion behind the traditional development approaches is that the projects are comparatively less complex, linear and predictable with clearly defined system boundaries which makes it simple to plan and follow without having any room for changes (Spundak 2014). Moreover, traditional development method depicts the requirements document as he key piece of documentation. The gathering of all the requirements, getting a sign off from the customer and then starting with the development of the project gives the project a limit of
Agile methodology follows iterative development method which make it more suitable to use for light weight projects where the changes are frequent. Waterfall on other case is a heavy weight methodology with no changes or iterations allowed once the project starts. Here the requirements are fixed and any change later is not accommodated and will be considered as a new project. Both the methodologies are adopted for a project based on its type and requirement. In this paper We have applied both Waterfall and Agile methods to a Service Delivery platform project of a telecom company to come up with an individual project plans
Software development is one of the highest demands in all over the world. We use software development techniques to solve the problems and to satisfy customers. Agile software development is a conceptual framework for software; it is also a group of software development methods based on iterative development. In 2001, agile software development was created by seventeen people with a desire to find alternative approaches to software development. The most important thing about agile methods are team work, conveying information to the team, face to face conversation, and satisfy the customer. There are various methodologies but I am going to describe the most popular ones.