Scrum methodology is an Agile management method approach toward software development as it progresses incrementally and repetitively.

1. Scrum Methodology IT400 Information Technology Architectures August 2011

2. Abstract: Scrum methodology is an Agile management method approach toward software development as it progresses incrementally and repetitively. The scrum method involves constant evaluation and reevaluation of the progression of a project, to insure it is completed on time, while meeting the specific needs as directed by the Product Owner. Scrum is unique to other agile methodologies in that it provides an empirical chart to track a product’s progression through all stages of its development.

3. There are three major roles in the Scrum methodology: Primary: Product Owner (PO): The person responsible for communicating and expressing the desired product ideas to the development team. Secondary: ScrumMaster (SM): The liaison between the PO and the production team. Tertiary: Production Team Members (PTM): Persons responsible for the completion of work on the project. Consists of cross functional teams of seven +, - 2 people

4. Steps in the Scrum methodology: Product Backlog: Master list of all functionalities of the project. Product backlog items are Managed by the PO. Usually written in a User Story format. Release Planning: The established list of goals, the order of their release, prioritization schedules, delivery date, and guesstimated cost. Composed of multiple Sprint Cycles. Sprint Cycle Planning Meeting: Held before and between each Sprint, which will consist of the PO and the PTMs determining what will be achieved in the upcoming Sprint. The Burn Down Empirical Chart will be generated which will reflect the production stages of the project. Focuses on high return on investment first. Sprint Cycle: Typically a 1-4 week time period during which a functionality is accomplished. Note: Sprint times may vary as milestones are reached or problems are encountered. Burnout chart: Show the average rete of productivity and velocity

5. The Scrum Process Schwaber, K. & Beedle, M. (2001). Agile software development with Scrum. Retrieved August 21, 2011 from the Visionds Web site: http://www.visionds.com/scrum.htm

6. SCRUM FRAMEWORK Idea Realization Unpredictable Large Complex

7. References: Dempsey, R. (2009). Introduction to Agile and Scrum: Parts 1 and 2. Retrieved August 20, 2011 from the agiledevwithrob YouTube Web site: http://www.youtube.com/user/agiledevwithrob#p/u/3/Ikug0qzkYF4 Kharytonov, S. (2009). Waterfall, RUP and Agile: Which is right for you? Retrieved August 20 from the ExecutiveBrief Web site: http://www.executivebrief.com/software-development/waterfall-rup-agile/ Murphy, C. (2004). Adaptive project management using Scrum. Retrieved August 21, 2011 from the Methods & Tools Web site: http://www.methodsandtools.com/archive/archive.php?id=18 McGovern, J., Ambler, S.W., Stevens, M.E., Linn, J., Sharar, V. & Elias, J. (2003). The practical guide to enterprise architecture. Upper Saddle River, N.J.: Prentice-Hall. N/A (2009). Scrum methodology: Learn the scrum methodology. Retrieved August 20, 2011 from the Collabnet Web site: http://scrummethodology.com/ Schwaber, K. & Beedle, M. (2001). Agile software development with Scrum. Retrieved August 21, 2011 from the Visionds Web site: http://www.visionds.com/scrum.htm Shojaee, H. (2008). Scrum master in under 10 minutes. Retrieved August 20, 2011 from the Axosoft YouTube Web site: http://www.youtube.com/user/axosoft#p/u/157/TWSXETDWGQ4 Spagnuolo, C. (2008). Agile vs Waterfall: A tale of two teams. Retrieved August 20, 2011 from the CSpag67 YouTube Web site: http://www.youtube.com/user/cspag67