Scrum Methodology
Learn the Scrum Methodology
The Scrum methodology of agile software development marks a dramatic departure from waterfall management. In fact, Scrum and other agile processes were inspired by its shortcomings. The Scrum methodology emphasizes communication and collaboration, functioning software, and the flexibility to adapt to emerging business realities — all attributes that suffer in the rigidly ordered waterfall paradigm.
Scrum Methodology
For many developers in the software industry, the agile methodology is nothing new. Most folks know that agile was a direct response to the dominant project management paradigm, waterfall, and borrows many principles from lean manufacturing. In 2001, as this new management paradigm began to pick up momentum, agile was formalized when 17 pioneers of the agile methodology met at the Snowbird Ski Resort in Utah and issued the Agile Manifesto. Their manifesto is now considered the foundational text for agile practices and principles. Most importantly, the manifesto spelled out the philosophy behind agile, which places a new emphasis on communication and collaboration; functioning software; and the flexibility to adapt to emerging business realities.
But for all of the strides the Agile Manifesto made in revising a philosophical approach to software development, it didn’t provide the concrete processes that development teams depend on when deadlines — and stakeholders — start applying pressure. As a result, when it comes to the nuts and bolts of running a team with agile every day, organizations turn to particular subsets of the agile methodology. These include Crystal Clear, Extreme Programming, Feature Driven Development, Dynamic Systems Development Method (DSDM), Scrum, and others. At my organization, we use Scrum and I’ve found it to be an incredibly effective management methodology for everyone involved, including developers and stakeholders. If you’re interested in learning about the other agile methodologies, there are plenty of resources out there. This blog is designed to provide some essential background for those who are new to Scrum.
What’s Unique about Scrum?
Of all the agile methodologies, Scrum is unique because it introduced the idea of “empirical process control.” That is, Scrum uses the real-world progress of a project — not a best guess or uninformed forecast — to plan and schedule releases. In Scrum, projects are divided into succinct work cadences, known as sprints, which are typically one week, two weeks, or three weeks in duration. At the end of each sprint, stakeholders and team members meet to assess the progress of a project and plan its next steps. This allows a project’s direction to be adjusted or reoriented based on completed work, not speculation or predictions.
Philosophically, this emphasis on an ongoing assessment of completed work is largely responsible for its popularity with managers and developers alike. But what allows the Scrum methodology to really work is a set of roles, responsibilities, and meetings that never change. If Scrum’s capacity for adaption and flexibility makes it an appealing option, the stability of its practices give teams something to lean on when development gets chaotic.
The Roles of Scrum
Scrum has three fundamental roles: Product Owner, ScrumMaster, and team member.
- Product Owner: In Scrum, the Product Owner is responsible for communicating the vision of the product to the development team. He or she must also represent the customer’s interests through requirements and prioritization. Because the Product Owner has the most authority of the three roles, it’s also the role with the most responsibility. In other words, the Product Owner is the single individual who must face the music when a project goes awry.
- ScrumMaster: The ScrumMaster acts as a liaison between the Product Owner and the team. The ScrumMaster does not manage the team. Instead, he or she works to remove any impediments that are obstructing the team from achieving its sprint goals. In short, this role helps the team remain creative and productive, while making sure its successes are visible to the Product Owner. The ScrumMaster also works to advise the Product Owner about how to maximize ROI for the team.
- Team Member: In the Scrum methodology, the team is responsible for completing work. Ideally, teams consist of seven cross-functional members, plus or minus two individuals. For software projects, a typical team includes a mix of software engineers, architects, programmers, analysts, QA experts, testers, and UI designers. Each sprint, the team is responsible for determining how it will accomplish the work to be completed. This grants teams a great deal of autonomy, but, similar to the Product Owner’s situation, that freedom is accompanied by a responsibility to meet the goals of the sprint.
The tension between authority and responsibility means that it’s hard for Product Owners to strike the right balance of involvement. Because Scrum values self-organization among teams, a Product Owner must fight the urge to micro-manage. At the same time, Product Owners must be available to answer questions from the team.
Comments Feed Reader's Comments
Leave a Reply
Newsletter Sign Up:
Recent Posts
- Results of an Agile Assessment
- Introduction to Scrum Video
- Complexity and cost of change
- Technical Debt – The High Cost of Change
- Strategic Vision and Scrum
- Agile and PPM – Q&A
- Estimating Earned Business Value on Agile Projects
- Building the Product Backlog
- Intro to Agile
- The Agile Manifesto and Twelve Principles
- The Daily Scrum; It’s a Good Habit to Make
- Obstacles to Enterprise Agility
- What is Scrum?
- Can CSMs and PMPs Get Along?
- Free Scrum Webinars
Categories
- Agile and Scrum (27)
- Agile Assessment (1)
- Agile Manifesto (5)
- Agile Principles (7)
- Scrum Basics (43)
- Scrum Discussion (26)
- Scrum Transitions (16)
- Uncategorized (7)
Archives
- January 2012
- December 2011
- November 2011
- October 2011
- November 2010
- September 2010
- June 2010
- April 2010
- March 2010
- February 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
Blogroll
- Agile ALM
- Agile Methodology
- Agile Programming
- Agile Project Management
- Eric Brown
- Free Project Management Software
- IT Today
- PM Student
Danube on Twitter
- Overheard from a Twitter post by @crispkianheckl
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @azwarnazz
- Overheard from a Twitter post by @LogicalB0T
- Overheard from a Twitter post by @WundrKaiBig
- Overheard from a Twitter post by @PayErickDog
- Overheard from a Twitter post by @gmurrel
- Overheard from a Twitter post by @anabelbosshart
- Overheard from a Twitter post by @JerDoug
- Overheard from a Twitter post by @JerDoug
Mike Me,
I think that is a very bad idea. Sorry. The daily meeting is very much NOT a status meeting. It is a time for team members to align with each other. having them email one person (what role are you? manager, SM?) will break the concept od self-organization and collaboration faster than you can say “waterfall”. Don’t do it. Have the tema members talk to each other. Every day, in as a direct way as possible.
agreed with Tobias.
A good article to learn the SCRUM methodology.
hi,
i have always been exposed to waterfall methodology….i have just joined a comapny tht uses scrum but a product owner has experienced challenges in reporting to customer wrt to delivery dates??…please help with the following:
1. How does one link scrum to the project plan i.e. my understanding is that even if u follow scrum, project plans and road maps must still be done?
2. how can product owner communicate progress to clients i.e. prodcut owner that i am trying to assist is being given task that are to be done on dailiy bases but doesnt know how those tasks link to the final product??
Hope i make sense.
Xhanti
Hi,
I am seeking employment with a company that uses the scrum methodology. I am familiar with the Primer methodology (PMBOK) and would like to learn more about scrum. Can anyone help point me in the direction. Thanks!!
In response to Jose, who indicated that using Scrum “sucks”, I’d say that it’s not Scrum that is not working, but the implementation that’s not working. For e.g., the responsibility of the ScrumMaster is to remove impediments that may prevent the development team from doing their job, not to micromanage the activities of the development team. Some of the overriding agile principles are to ensure the customer is getting what they actually asked for, and to keep the lines of communication open. You’re trying to prevent surprises by ensuring that EVERYONE knows what is happening on the project at all times. Scrum and other agile methodologies were designed to prevent what occurs on many waterfall projects, which is that you don’t find out the project is way off course until too late in the lifecycle, wasting time and money.
My suggestion is to look at how Scrum has been implemented in your organization, compare it to what Scrum teaches, see where the differences are, and modify your implementation to align with what the methodology teaches. You may find that you’re not really doing “Scrum” even though you say you are.
Gain – I would recommend reading this website and also check out popular blogs like blogs.danube.com
Here’s a blog post for Gain as a starting point!
http://blogs.danube.com/your-career-in-scrum-pathways-to-starting-a-scrum-career
Is Scrum methodology useful for a testing project?
Scrum 101 explained at its best. Thanks. I feel Agile methodologies like scrum needs to be implemented at every level in the company not just development.
Hello all,
I am brand spanking new to the Scrum world. I am traditionally a WATERFALL guy and I am very confused on where testing fits into the scrum methodology. I understand the sprint cycles and all that and I understand that the code is developed to pass the tests. I guess where I am confused is in shorter sprints, say for instance, a one week sprint, where SQA run the intergration tests or the regression test.
Is this how it works or am I missing something here? Say we have a 1 week sprint.
** Mon – Wed (Developement of the test and the code.)
** Thurs – Friday (Integration/Regression testing as well as a product demo)
I am assuming that if this is the general idea that the SCRUM methodology relies heavily on automated regression testing, is this a correct assumption?
Thanks in advance for ANY help.
Thanks Ryan for the comments here is my recommendation:
QA & Scrum Blog posts here:
http://blogs.danube.com/scrum-and-quality-assurance
http://blogs.danube.com/junit-is-not-just-for-unit-testing-anymore
http://blogs.danube.com/generalists-vs-specialists-revisited
If you need more – just ask!
It’s a very good article. Just please let me know that using scrum, whether there is need of Tech Lead/Project Lead/Project Manager.
very well written summary …succint and clear..Thanks.
Great article, great questions, and great group commentary and advice.
I am running an Agile project as the scrum Master and we have had a great amount of success. This is a project that was stopped or put on hold twice over 2 years in Waterfall. We started Scrum in July of 2009 and have a final first release of our solution rollibng out to 10% of our locations (about 800) now through March. We have a complex solution, a team of sub small teams because of skill sets of their focus and anagressive timeline. We also had external vendors participating or owning some of the development. We are very happy with our results in 6 months. Here is my 2 cents:
- Read Mike Cohns Toward a Catalog of Scrum Smells. We hit all of these.
http://www.mountaingoatsoftware.com/articles/11-toward-a-catalog-of-scrum-smells
- The Product Owner Role is Key. Ours was involved and Co-located with the team 95% of the time. It made all the difference in the world.
- The preson that alked about Scrum not working in a environment where team mebers get pulled away to do support a lot We have that bad. We made it work. The scrum Master must get involved every time and be creative, negotiate.
- Those thinking of entering the scrum world, it helps to have some PM background but I would recommend you try. The best projects I have ever been on were those of colocated groups where collaboration and team work was the approach. Scrum Agile is a lot of fun and very rewarding. Not to mention efficient and sucessful.
QUESTION- Scrum is new to us and we did not follow it to the “T” but were adapted it “Cafeteria style” took what we felt we needed and it worked. My shortcoming is – How do you measure your progress from the beginning and forecast an end date when you never really know the complete picture or workload? Requirements evolve, scope expands (does not always creep)or becomes more robust, that makes it difficult to see what you have in front of you. The siza of the elephant if you will. We measure team hours burn against the project and timeline burn. I expect you will tell me that when we run out of time/money, we need to request new approval to move forward from what we have accomplished so far. I believe that is where we are at and I have no issue with that, I just would like a better metric on Progress through sprints as it relates to the Product Backlog
Thank s alot for this site.
Hi,
To answer Ryan’s question, in my team, the test team is 100% automation. We dont have any manual tests happening unless there is any automation-tool limitation. What this means is:
Each team has a tester (couple of them) and s/he’s a part of the pre-sprint planning and the daily scrum from which s/he knows the tasks and starts identifying/ designing the automation scripts for the functionality developed the previous day or the one which is going to be developed the same day (which also means the wire-frames or cut guides must be ready to automate). So the cumulative automation scripts are run twice or thrice within the 1-week sprint (we have 2-4 weeks sprints here). Another point is that unless there is automation, the test team will not be able to give a decision for that sprint’s deliverable within the sprint time. Hope this helps. If not, do add in your question here
@ScrumDog – I would read through Michael James’s macro-measurement white paper here: http://danube.com/scrum/whitepapers
Hi,
This article is really helpfull. Thnaks for posting. If somebody can explain this thru some diagram it whould be wonderfull
Really nice and helpful article. It clear all the queries in my mind.
Hi!
Thank you for a nice article. Can scrum be applied as a project management in general, not only software development?
What are the requirements for scrum to be sucesfull? (if you don’t consider the implemetation part..)
I’ve been testing for about 10 years but have only heard of Scrum in the last few months. Probably because I’ve been stuck bouncing around between contract positions for a very long time. As a contract employee I don’t usually get involved with the processes a company is using, I am there just to fill a short-term need. I feel like I’ve been in a cave for about 5 years!
All that to say that this was a great article and I now I have a basic understanding of Agile/Scrum and can at least follow a discussion. I’m not sure when I will actually get the opportunity to learn about Scrum first-hand. I guess it all depends on the job market.
I appreciate all of the insightful questions and answers and I look forward to learning more. If any of you folks are looking for a good blackbox tester with little knowledge of Scrum then I’m your man!
Good introduction on SCRUM. Explained nicely to understand. How do we compare CMM with Scrum.
Neat and precise explanation. Best of all, even the newbie can grasp important aspects of Scrum. Very good posting. To the most part, the visitors to this website shared their knowledge / questions and one way or other, enriched the entire group. Thanks to admin for answering all the questions asked.
I am really very much thankful to you for scrum tech.
it is presented nice way to understand as well as implement.
It was a fab article on SCRUM. Thanks!!!
Jose,
Here is a case study for your questions. Maybe, you will pick up soome points from it.
Read, “Distributed Scrum: Breaking the geographical and cultural barriers” at
http://evilword.wordpress.com/
abyjos
Great Article.
Where do Coaches and Managers fit into this equation. I believe, Coach is the Scrum master. Is there anything called as a Tech Lead or will that be a Team Member.
-S
Why we use small team in scrum please any body reply my answer , why scrum reliable only small oragnization not big why please reply answer if any body know
This is very nice article on scrum also a very good discussion. I’m new on scrum and Agile. Going through study on these and wants to do certification. If someone can suggest , what should be the ideal way to start getting experience on scrum?
Best,
Ravi
I am new to the Scrum Methodology and would like to know if it could be adapted to something other than software development, i.e. Business Processes. I deal mainly with government contracts developing integration of business models and practices within bureaucratic enivronments, I utilize a project management tool which is cumbersome and time consuming.
What is the ratio od developers to QA in 4 week sprint?
How could QA overcome the problem of regular requirement chnages in scrum, means how to handle testing in such scenario when requirement keep chaning regularly?
Amol J
it very nice summary.rellay help full topic.
Thank you.
Murali Krishna
Very helpful article!! I am very new in QA industry. Thanks.
it’s a awesome post.
Very nice article and discussion thread indeed.
Any suggestion on how to avoid the situation where “The Daily Scrum feels like it is a status update from the team members to the ScrumMaster”
Anupam
Hi to All,
It’s been very good blog for those who wnat to know what actully SCRUM can do for us.
For the Scrum enthusiasts in Bangalore, Certified Scrum Master Training Program is being held on Aug 26th & 27th.
Visit http://csmbangalore.doattend.com for more details on the Program.
Shanthi B
I had to read your post three times to get the full meaning of it. I enjoy reading what you have to say. It’s unfortunate that more people do not understand the benefits of coaching. Keep up the good work.
Hi all, just a comment on SCRUM. For me, Scrum is an art. You need to practice it to develop your skills. It is good to have a starting point (framework) but the skills of the people will make the difference. In complex situations, SCRUM is necessary to succeed but it is not enough. Just wanted to share a thought with you all.
SCRUM is invented to squeeze dry software engineers, maximizing productivity, minimizing costs, putting developers under maximum pressure continuously. Business Universities are breeding a new type of money hungry manager like blood thirsty sharks disregarding their victims.
That’s what our young ICT professionals should learn from older professions like lawyers & doctors, not to accept being dictated & treated like slaves by heartless and ignorant people.
SCRUM is only seen with bad employers / clients that set foolish deadlines, draining all the creativity and energy the developer has left to engineer extremely complex processes.
SCRUM = SCUM !!!
Hi,
This was a very well thought out article and good reading. However, I would like to point out that the principles of Scum is not a new concept and should not be confined to Agile or software production; as its principles and methodologies are universal and can be transferred to any project or management situation.
Conceptualising Scrum suggest that it is really based on a managers attitude towards his or her role as either as a manager/controller or a facilitator.
Considering the managers role as a facilitator in any context or situation means that the principles of Scrum by definition have to be applied. Facilitators by nature clear the path for other people to succeed and shine through their endeavours.
The management aspect of the job is really just an over stated team leadership/coaching and administrative function that people with an autocratic management style do not seem to comprehend.
To be honest I have been practicing these principles since the early 70’s and it is nice to see that attitudes towards managing the efforts of workers has and is continually improving over time.
Kind regards
Stephan Toth
HI All,
It was a good/brief summarization of what the Scrum Org structure of Agile methodology.
looking to read more & learn to be implemented in the Agile project we are working now.
Regards,
Ashok
This could use more concrete information. You give some bullet points of the history, features, and overall philosophy of scrum, but you don’t really explain how the process works. What about the product and sprint backlog? What about daily standup? More details on how it all works in real life would be good.
its really a good blog for Basic info of SCRUM
Nice easy to understand and very used friendly. What does it take to get certified in Agile?
Very good post to start up for good Agile Methodology like Scrum….
Excellant article and very informative comments too!
But I’m confused by the Project Manager vs. ScrumMaster terms/roles. In a comment above by the site Admin on Jun 9, 2009, they state:
Technically, the ScrumMaster is on the Scrum team, but is not a part of the development team. Having said that, the ScrumMaster should definitely not be the Project Manager (or Product Owner).
Yet in the description of the ScrumMaster Certification course that this site links to it states:
An agile project manager emphasizes facilitation, leadership and communication over traditional command-and-control activities. In the Scrum framework, this role is called “ScrumMaster” as a constant reminder of the differences between agile and traditional project management.
So is the ScrumMaster the PM or not?
The major flaw I see in the SCRUM process is the ability to be predicable as to when a release can go out the door with a predetermined set of features. SCRUM is great at flexibility but when senior management wants to know when product X will be delivered and the delivery date is at least 6 months away, SCRUM does not help much. I have been working at a company that has been attempting to use the SCRUM process (poorly with very little to no training and no experienced agile coaches) for about 18 months now and I can see the value in the process but I don’t see how it helps with the predictability out pass a few sprints.
Nice presentation. Do we get such type of training in India ?
Hi Guys,
Could some one explain indetail What are the Roles & Resposibilites of a QA in Scrum Team?
Thanks,
Chinni20
Very helpful information on Scrum. Thanks
Keep up the good work!
Very nice presentation.. and good discussion. Could some one help me to get the Steps and Challenges to migrate an existing Waterfall Release delivery Model to Scrum Delivery.. Thanks much – Kiran Sripada
Are there any testing automation tools for testing Oracle development projects using PL/SQL packages. We are looking to implement scrum on an Oracle project but do not have any automated testing tools.
Any suggestions will be helpful
As I understand, SCRUM in ONLY about project management — it is silent on software engineering. Folks use Extreme Programming (XP) or FDD as frameworks for Software engineering.
I believe, combination of SCRUM + XP is most widely used and popular…
Can you share your thoughts?
Scrum makes sense, but isn’t the Scrumaster (CSM) just a glorified secretary? They seem to make good money, but the real work is by the PMs, Tech Leads, and Developers. What justifies the high Scrumaster pay when the job is actually just a glorified secretary. The glorified secretary is all that the “old school” IT managers were, although they never performed the collaboration role across groups/teams.
Nice Article about the SCRUM !!
can anyone say how frequently code review can be done within a sprint to make the story as Done.
pls share me the best approach to be followed.
Thanks.
Where do Coaches and Managers fit into this equation. I believe, Coach is the Scrum master. Is there anything called as a Tech Lead or will that be a Team Member.
Project Management Training
Any one suggest me , research topic for software engineering. so i make my assignment.
Where does the IT Business Analyst (the BA role as defined by the IIBA and Business Analysis Body of Knowledge (BABOK) fit into the Scrum approach? It might be said that there is no need for a BA on Scrum, but I have found that it is necessary to have someone on-board who is trained to elicit requirements from stakeholders in an analytical way. With our clients, I find this person coming from the business side in about 1/2 the cases and from the tech side for the other half. The best fit seems to be the Product Owner in Scrum, though a case could be made for the BA being the one doing analysis within the Team. Any thoughts?
Genuinely educational thanks, I believe your trusty followers will probably want significantly more reviews such as this maintain the good work.
I see CollabNet is running a webinar later this week talking about the integration of Project Portfolio Management and Agile Project Management. This could be interesting.
Howard,
A few random thoughts on your post: I can certainly see the benefit of formalized requirements (backlog) collection and refinement. That said, we Agilists favor action over planning, so comprehensive, all-complete requirements management (as in Doors, Dimensions RM, RequisitePro, et al) is not really the way to go. If the BA is not the Product Owner, he’ll act in a supporting role to the Product Owner as a stakeholder. The PO has ultimate say in what backlog items are prioritized, but I think the work of a BA could help inform his decisions and make him a better PO.
Hi,
Thanks for the great info on the scrum methodology i understand it a little more now,
I have never witnessed SCRUM working — ever! Any project that started out as ‘agile’ but ultimately succeeded did so only because common sense finally set in and the decision makers decided to abandon the fad.
I’m convinced that the following video hit the nail squarely on the head as to why any company has ever attempted agile:
http://www.youtube.com/watch?v=nvks70PD0Rs
John
The most widely acknowledged certification outfit for Agile comes from the Scrum Alliance. To get certified as a ScrumMaster, Product Owner or other, you’ve got to attend a course delivered by a certified Scrum Trainer and then take their test. CollabNet offers certification courses – check them out here.
Agile, among the rest, has worked out for my projects. Easier resources allocation and reduce risk of not meeting deadlines because of minor yet critical issues.
Hello iam abdullah raza lakhan i done so many research on paper on the agile scrum i want to share my research to all people even i want to uplaod ,i have lot of experience on agile scrum how to use it over web industry
Nice Article on scrum
Is it affordable for a startup company to adopt Agile Methodology ??
I would argue that Agile is uniquely suited to a startup, and that its a far more cost effective means of building software (or whatever) than traditional plan-driven approaches.A few reasons for this, off the top of my head:
1. Small companies tend to have people that wear many hats. The cross functional teams in scrum are just that – cross functional;
2. Agile/scrum is iterative. You don;t need to wait for the whole thing to be done before getting software into production. Each iteration delivers value.
3. Small companies cannot affords to misfire on quality. Scrum is far better suited to delivering quality and on-target releases than traditional approaches.
I have little knowledge about Scrum. One thing that I wonder in Scrum methodology is: Where do The Product Manager, Project Manager, Team Leader fit in the Scrum?
The Product Manager seems to fit with the product Owner and that is fairly ok.
Now Project Manager if fits into the Scrum Master, then it seems there is no scope of a Team Leader or sometimes Engineering Manager in Scrum. Does Scrum tries to eliminate Team Lead out of Scope?
I’d caution about making direct, one-to-one comparisons between the roles of a plan-driven approach and the roles in Scrum. Making those comparisons are all too simplistic, and often incorrect. Moving to Scrum often entails moving away from those old roles.
A traditional project manager is all about command and control. A product owner in Scrum is more about keeping the team on track with his vision by building and maintains a prioritized backlog, and helping the team collaborate. A ScrumMaster’s primary role is to protect the team from inbound distractions and help them overcome impediments. The ScrumMaster does not assign tasks – the teams self organize and self-assign tasks. He also helps facilitate the crucial meetings – daily standups, sprint reviews and retrospectives. The ScrumMaster should be the only communications conduit to the team from outside. But again, the ScrumMaster does not assign tasks -something that in a traditional model was handled by a Team Lead.
It is scary to eliminate these traditional roles, but it works.
testing
There are popular agile methods- Extreme
Programming (XP) and Scrum
Scrum is software development process, it is iterative and incremental frame work for the project management and it is a process frame work which contains set of practices and predefined rules.
The main roles of the scrum are 1.product backlog 2.Release planning 3.sprints 4.Burndown charts and 5.Tracking bugs
1. Product backlog is a high level list that is maintained throughout entire project. It aggregates backlog items
In product backlog the feature list means users, customers, executives, developers and testers the collection of all feature lists is product backlog they think how to make product great.
Hear product owner and scrum masters have key roles of the product.
Product owner: Put the right functions into the product.
Scrum master: Scrum master maintain the project progressing smoothly and every member doing they job right or not and conduct meeting and planning’s and releases.
Developers build the product
And testers make sue to work right
Next come to release planning
2. We work on the feature list the outcome is release backlog
Scrum master provide the rough idea of release. He estimate the work in to the time intervals means hrs and minutes like that
Next sprints
3. Sprints: In agile methodology we come up with the small sprints of work and keep implementing in 2,3 weeks depends this is advantage and we save time and money
Sprints generally range from 3 to 30 lengths depending on project release cycle. In sprints we divide the work into features. Some sprints have big features and some have small features it depending on that
The main goal of the product release is we do 100% work on the sprint, the late finish of sprints indicate project is not going smooth.
4. Burn down charts: It’s a day by day measure project progressing. It shows project is on the track or be late.
5. So what about bugs
We track bugs separately like we kill first sprints of bugs after that sprint, and 2nd sprint of bugs kill after that sprint but if any showstoppers or any high priority bugs are resolved in same sprint, medium and low level bugs will be prioritized in the next coming sprint.