What Does Scrum Stand For? written by: Ronda Bowen • edited by: Michele McDonough • updated: 5/29/2013 You may have found yourself wondering what "Scrum" stands for. This article answers that question and other questions the newly initiated may have about Scrum when implementing it into their work environments. A Rugby TermThis is one of the most common questions asked about Scrum. Understanding Scrum - Part I This series of articles details the principals behind scrum methodologies - the process, environment, process, roles, etc. Agile Software Is A Cop-Out; Here’s What’s Next Never has a new trend annoyed me as much as Agile. Right from the get-go, the Agile Manifesto revealed the weaknesses and immaturity of the founding principles. The two most disturbing: “Working software is the primary measure of progress” and “Business people and developers must work together daily throughout the project.” Using “working software as the measure of progress” is narcissistic. Yikes. A New Thesis For A Better Approach To Software DevelopmentFor the future of application development to be insanely great user experiences, we need a new software development methodology. Parallel. The parallel, immersive software studio is different from other methodologies in five important ways: Software is not code. This post about parallel, immersive software studio (STUDIO) can’t compete with the 1,813 books about Agile Software on Amazon.com right now. As always, I welcome a vibrant discussion! NoteI initially wrote about this new approach in December 2008. Recommended reading:
FAQ Training and Certification FAQ Sections General FAQ Why does Scrum Alliance offer a certification program? What makes the Scrum Alliance certification program different from other Scrum training programs? Can I become certified without taking a course? Certified ScrumMaster® What does it mean to have a Certified ScrumMaster® (CSM) designation? Does Scrum Alliance offer an online CSM course? The Certified ScrumMaster® courses engage participants in live, interactive learning, free from the obstacles inherent in an online activity. Do I receive PDU credits for a CSM course? What is the membership fee? How do I renew my CSM? Please visit How to Renew Your Certification and Membership for detailed instructions regarding how to renew your certification. Whom should I contact if I have additional questions? Why has Scrum Alliance added a Certified ScrumMaster® test? Do I have to take the CSM test to become certified? Can I retake the test if I score poorly? Where can I find the link to take the CSM test? How do I apply?
Scrum Log Jeff Sutherland Agile Epic Board : Agile101 – Agile Project Management and Digital Publishing Aside from being the high point of a visit by a number of McKinsey Management Consultants (who apparently stopped to take pictures – no joke), the Epic Board also got the nod of approval from Howard Averill, CFO of Time Inc. Continue reading Although I use this board to track our development programme across multiple products, teams and sprints, the Epic Board can also be a very useful project management tool. See The Epic Board – An Essential Project Management Tool. I introduced the Epic Board as a programme management tool – a tangible release plan that can help you to plan software development programmes comprising multiple separate projects combined with Business As Usual Activities. The more I use the Epic Board, the more I love it. Make no mistake about it, I don’t think this tool should (or could) replace a Scrum Task Board – it’s totally different… Continue reading
Agile Principles and Values, by Jeff Sutherland Individuals and interactions are essential to high-performing teams. Studies of "communication saturation" during one project showed that, when no communication problems exist, teams can perform 50 times better than the industry average. To facilitate communication, agile methodologies rely on frequent inspect-and-adapt cycles. These cycles can range from every few minutes with pair programming, to every few hours with continuous integration, to every day with a daily standup meeting, to every iteration with a review and retrospective. Just increasing the frequency of feedback and communication, however, is not enough to eliminate communication problems. These inspect-and-adapt cycles work well only when team members exhibit several key behaviors: respect for the worth of every person truth in every communication transparency of all data, actions, and decisions trust that each person will support the team commitment to the team and to the team’s goals
Implementing Scrum – PowerPoint Presentation After seeing how popular my last presentation was (10 Key Principles of Agile Software Development) – and following numerous requests to do another one – I’ve created this PowerPoint presentation about ‘Implementing Scrum’. This presentation follows my latest series about How To Implement Scrum in 10 Easy Steps. It goes step by step, with pictures and notes on each slide from my blog. The notes are not intended to be a script, but should hopefully still be very helpful. When you buy this presentation for $15, you will also get access to my last presentation free of charge! If you purchase this presentation, all I ask is that you credit allaboutagile.com as the source, do not publish it (in print or on the web) and please do not circulate it (please direct people to this address). I sincerely hope you find the presentation useful – for $15 you can’t really go far wrong! P.S. you can get both of these presentations free if you buy my 55 page eBook . Kelly. Home
Agile software development Agile software development is a set of principles for software development in which requirements and solutions evolve through collaboration between self-organizing,[1] cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change.[2] Agile itself has never defined any specific methods to achieve this, but many have grown up as a result and have been recognized as being 'Agile'. The Manifesto for Agile Software Development,[3] also known as the Agile Manifesto, was first proclaimed in 2001, after "agile methodology" was originally introduced in the late 1980s and early 1990s. The manifesto came out of the DSDM Consortium in 1994, although its roots go back to the mid 1980s at DuPont and texts by James Martin[4] and James Kerr et al.[5] History[edit] Incremental software development methods trace back to 1957.[6] In 1974, E. The Agile Manifesto[edit] Agile principles[edit]
Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams.
Manifesto for Agile Software Development OWASP Home - Web Application Security Consortium