Scrum is an agile framework for managing projects, especially software development. It uses short iterations called sprints to rapidly develop features. At the start of each sprint, a product backlog prioritizes features and the team selects what they can complete. Daily stand-up meetings help the team track progress and remove impediments. At the end of each sprint, working software is demonstrated for feedback before beginning the next sprint. Agile practices like Scrum aim to adapt quickly to changing requirements through transparency, inspection, and adaptation.
3. The System Development Process Requirements Analysis System Design Program Design Program Implementation Testing Delivery Maintenance What is the problem? What is the solution? What are the mechanisms that best implement the solution? How is the solution constructed? Is the problem solved? Can the customer use the solution? Are enhancements needed?
4.
5. Murphy's Law: Things will go wrong in any given situation, if you give them a chance.
11. Scrum Scrum is an agile process for developing software. With Scrum, projects progress via a series of month-long iterations called sprints . Scrum is ideally suited for projects with rapidly changing or highly emergent requirements.
12. Product Backlog The Product Backlog is the master list of all functionality desired in the product. When a project is initiated there is no comprehensive, time-consuming effort to write down all foreseeable tasks or requirements.
13. Product Owner The Product Owner is typically someone from a Marketing role or a key user in internal development.He commits that he or she will not throw new requirements at the team during the sprint. Requirements are allowed to change (and change is encouraged) but only outside the sprint .
14. The Scrum Team Scrum teams do not include any of the traditional software engineering roles such as programmer, designer, tester, or architect. Everyone on the project works together to complete the set of work they have collectively committed to complete within a sprint.
15. The Sprint Begins The Sprint Planning Meeting is attended by the Product Owner, Scrum Master, the entire Scrum Team, and any interested and appropriate management or customer representatives.
16. During the sprint planning meeting the product owner describes the highest priority features to the team. The team asks enough questions during this meeting so that they can go off after the meeting and determine which tasks they will move from the product backlog to the sprint backlog.
17. Sprint Backlog The sprint backlog is the list of tasks that the Scrum team is committing that they will complete in the current sprint.
22. Sprint Review Meeting Typically, this is a demo. It should be a natural result of the sprint. Participants in the sprint review typically include the Product Owner, the Scrum team, the ScrumMaster, management, customers, and engineers from other projects.
23.
24. Extreme Programming Continuous integration, relentless testing. Smalltalk: "Code a little, test a little" Coding ain't done 'til all the tests run.
29. Test thoroughly. Introduce bugs on purpose. There is no perfect program, and you will never catch all the possible errors. Let the first time you find a bug be the last time you find that bug.
32. Conclusion The success of a project is measured by how well it meets the expectations of its users. Never lose sight of the business problems your application is intended to solve. Give the users a bit more than they were expecting.
33. Eversun Software Philippines Corporation 5 th Floor, Djongjin Bldg. Valeria Street, Iloilo City Web: http://www.agentsofvalue.com My email: rex.a@agentsofvalue.com Our Company Phone: 338-3106, look for Mia