Bsa 385 Week 2

The goal of this study is to collect, analyze, and interpret my variable expenses to increase my monthly savings. I will expose key variables, unnecessary expenditures, and develop a plan to manage those spending habits. The escalation of my variable costs has prevented me to increase my savings account, which has directly prohibited my efforts to make extra payments toward my investment property.

Big Corporations and Health care organization are always looking to improve their information systems to save time, money, and people lives. One most used information system would be the System Development Lifecycle (SDLC). A system development can sometimes run over budget or the corporation and organizations will never receive full satisfaction if their goals are not accomplish.

The preferred methodologies for managing a software’s lifecycle are a major factor in deciding how a firm reacts to market demands. The major SDLC frameworks followed are the waterfall model, Agile methodology (scrum) and Kanban. We will discuss this answer

The life cycle of the system can be designed and analysed with SDLC (system development life cycle). SDLC is an identifiable system for following-up on the planning and announcing the organization of “Family Pet’s” objectives to improve and maintain organization operations for events. The standard step are plan/select a system, analysis the system, design the system, and implement/operation the system. Furthermore, “Family Pets” is a small business looking to improve the functions of events by organizing conference, seminars, and parties. The system will be called “Love.” A system is the interrelated set of business procedures used within one business unit working together for some purpose. The purpose of “Love” is to develop the company's growth by adding new clients/customers, promotion/advertising, develop skills, advance knowledge, and purchase new products for procurement. The goal is to have quality level operation based on demands and supply resulting in more profits from customer loyalty. Also, the outcome will be that the objectives, structure, and process will be simplified with knowledge of how to exploit information by all employees. The parts of the system to “Love” are components, interrelated components, boundary, purpose, environment, interfaces, constraints, input, and

Another important part of Scrum is the Sprint Planning. It takes place before the start of a new Sprint's with all participants (Scrum Master, Product Owner, Development Team). In a Sprint Planning, User Stories are selected from the Product Backlog. The stories are prioritized based on the estimated bene ts and moved to the Sprint Backlog. In the Sprint Backlog maximum user stories in the value were taken by 11 story points. This ensured that the sum of the estimated story points does not exceed the capacity of the development team.

A scrum master makes sure that the team is functional and productive. A cross-functional team self-organizes to get the work done (Meier & Ivarsson, 2013). Ceremonies include sprint planning, daily scrum (aka daily standup), sprint reviews and sprint retrospectives (Meier & Ivarsson, 2013). During sprint planning, the team meets with the product owner to select a set of tasks to deliver during a sprint. In a daily scrum, the team meets every day to share any roadblocks and progress. At sprint reviews, the team demonstrates what has been completed during the sprint. Sprint retrospectives are held so the team looks for ways to improve the product and the process (Meier & Ivarsson, 2013). Artifacts are; product backlog, sprint backlog and burn down chart (Meier & Ivarsson, 2013). A product backlog shows the prioritized list of desired project outcomes/features. A sprint backlog includes a set from the product backlog that team agrees to complete in a sprint, broken into tasks. A burn down chart depicts the remaining work (Meier & Ivarsson, 2013).

The book is entitled “Scrum The Art of Doing Twice The Work in Half the Time.” The authors talk about the typical format for business being a waterfall method. A department for each stage of production. For example, a department that finds projects, a department that decides what the specs/goals should be, a department determines how long that may take, a department to create the project, a department to test, a department to sell. The authors argue is that this is incredibly ineffective. Rather than having departments they suggest having teams with all the skills combined. A team that consists of one person from each department, i.e. a group that works cohesively. By doing so, they speculate that you can eliminate communication issues, time delays, and confusion produced from a waterfall method.

The team and Scrum master select a section of items/features from the top of the product backlog that can be achieved in the sprint duration.

SC will compare traditional and various iterative implementations of the SDLC. For example, Braude and Bernstein (2011) state that the popular and mature waterfall process model promotes simple comprehension, project management, and resource distribution of small project development lifecycles. The serial nature of the traditional SDLC leans toward the gathering of all requirements at the beginning of the project whereas the majority of testing occurs at the end of the lifecycle. The waterfall model’s linear design creates disastrous risks for large projects if the project team does not understand the core requirements during the initial phase of the project or the detection of major problems occurs toward the end of the project. On the other hand, a spiral model significantly reduces risks for large projects whereas complexity causes overkill for smaller projects. The project’s physical scope, timeline, budget, and resource determine which the most optimal process model for a project. Table 1.1 displays a comparison chart that SC uses to weigh advantages and disadvantages of traditional SDLC and Agile development methodologies. SC will utilize this chart to determine which development methodology is utilized based on the primary amount of questions answered positively weighed with the clients business case requirements. “Agile software development is a

Agile development is used in a team of five – six developers which work closely together and interact with each other. Before the project starts user requirements are collected from the user. The scrum master will be responsible that the whole team works and also get the customer involved to get more feedback for the project. This is a very good approach because the developers can share their knowledge and learn new skills from each other. The team member should be highly skilled in order to work together to avoid any lack of skills in the development.

Scrum is a simple framework used to organize teams and get work done more productively with higher quality [7]. Scrum provides a productive working environment in which it allows teams to choose the amount of work to be done and how to best complete the work. The application of Scrum enforces a few simple rules that have the potential to make a team self-organized into process that can achieve 5 to 10 times the productivity of a waterfall based process [5]. Scrum focuses on prioritizing work based on business value, improving the usefulness of what is delivered, increasing revenue,

These iterations typically last one to four weeks and can almost be seen as small projects with actual deliverables (Sindhgatta, Narendra & Sengupta, 2010). Sindhgatta, Narendra and Sengupta (2010) embarked on a case study based on the Scrum agile methodology. Two key roles are the ScrumMaster and product owner. The ScrumMaster is responsible for helping the development team use the Scrum framework and the product owner is the liaison between the development team and the business or end users (Sindhgatta, Narendra & Sengupta, 2010). At the end of each sprint, code is delivered and tested, and feedback is looped back into the model. This is in stark contrast to the waterfall method and facilitates the likelihood of constant change in the agile model (Sindhgatta, Narendra & Sengupta, 2010). As a project evolves, members of the development team and the business may get a better understanding of the requirements which can lead to changes in code that may have already been created as part of earlier sprints (Sindhgatta, Narendra & Sengupta, 2010). This concept of project evolution with changing requirements needs to be allocated into the project schedule as extra time for recoding and retesting (Sindhgatta, Narendra & Sengupta, 2010). This extra time is not something that is built into a waterfall model because the requirements should be a static entity and rework should not be an option

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].

Scrum (link to the page http://en.wikipedia.org/wiki/Scrum_(software_development)) is a project management methodology. It is mostly used in I.T. and Software Development. Scrum is an iterative and incremental variant of Agile (link to http://en.wikipedia.org/wiki/Agile_software_development) Software Development Methodology that was created by Ken Schwaber (Link to http://en.wikipedia.org/wiki/Ken_Schwaber) and Jeff Sutherland (http://en.wikipedia.org/wiki/Jeff_Sutherland) in the 90's. S

Computer system plays an important role in solving human problem in their daily life. There are standard steps in order to develop information system called System Development Life Cycle (SDLC). SDLC is the framework available to build a complete system. There are five phases in SDLC which are planning, analysis, design, coding, testing and maintenance (refer to Figure 1 in Appendix 1).