Agile , SCRUM
Introduction
What is Agile Methodology?
What is Scrum?
History of Scrum
Functionality of Scrum
Components of Scrum
Scrum Roles
The Process
Scrum Artifacts
Scaling Scrum
Q & A Session
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
White Paper: Agile Web Development & The Scrum ProcessMagic Logix
To be agile is to move swiftly or quickly. This term has recently popped up within business and management terminology. However, the phrase moves well beyond a buzz term (sorry for you fans of ‘synergy’ out there – agile actually conveys some real meaning). This whitepaper is here to clarify just what the agile approach and attitude is, define the scrum process associated with this school of thought, and to provide real life examples of just how it’s effective.
Can agile frameworks help small development teams? After looking at some agile basics, I examine two projects where a small development team used scrum. Agile can be used by small teams to their advantage with commitment and some work.
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...Ed Kozak
The work breakdown structure (WBS) is often one of the most overlooked artifacts in any project but it's also the most important for project success. The schedule, budget, resource requirements, risks, and communication plan all are derived from the WBS. Many project failures--over-budget, poor quality, incorrect functionality, delayed schedule--can be traced back to a poor WBS. Failure to plan is planning to fail. How does your organization stack up?
My thoughts on Agile and how it helps in successful product delivery as guest speaker for Graduate level course : Innovations and Entrepreneurship in the Information Industry taught by Nancy Gilby
Overview of SCRUM development process. I put this together to present to my company/group.
Most slides are "borrowed" from Alan Shalloway's presentation.
Agile , SCRUM
Introduction
What is Agile Methodology?
What is Scrum?
History of Scrum
Functionality of Scrum
Components of Scrum
Scrum Roles
The Process
Scrum Artifacts
Scaling Scrum
Q & A Session
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
White Paper: Agile Web Development & The Scrum ProcessMagic Logix
To be agile is to move swiftly or quickly. This term has recently popped up within business and management terminology. However, the phrase moves well beyond a buzz term (sorry for you fans of ‘synergy’ out there – agile actually conveys some real meaning). This whitepaper is here to clarify just what the agile approach and attitude is, define the scrum process associated with this school of thought, and to provide real life examples of just how it’s effective.
Can agile frameworks help small development teams? After looking at some agile basics, I examine two projects where a small development team used scrum. Agile can be used by small teams to their advantage with commitment and some work.
The Work Breakdown Structure: Lack Of A Good One Already Sets Your Project Up...Ed Kozak
The work breakdown structure (WBS) is often one of the most overlooked artifacts in any project but it's also the most important for project success. The schedule, budget, resource requirements, risks, and communication plan all are derived from the WBS. Many project failures--over-budget, poor quality, incorrect functionality, delayed schedule--can be traced back to a poor WBS. Failure to plan is planning to fail. How does your organization stack up?
My thoughts on Agile and how it helps in successful product delivery as guest speaker for Graduate level course : Innovations and Entrepreneurship in the Information Industry taught by Nancy Gilby
Overview of SCRUM development process. I put this together to present to my company/group.
Most slides are "borrowed" from Alan Shalloway's presentation.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
the presentation gives brief description about a methodology of software engineering which is most using software engineering process in today's IT world and helps student to know how a software company runs and build software product using various software engineering methodologies.
this is the document in PDF format used as documentation for technical seminar on Scrum called as Proffesional Scrum Master which is a certificate on Agile Software development process.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
Scrum Overview for Agile Software Development. ... Scrum is a project management framework that is applicable to any project with aggressive deadlines, complex requirements and a degree of uniqueness. In Scrum, projects move forward via a series of iterations called sprints. Each sprint is typically two to four weeks long.
Meeple centred design - Board Game AccessibilityMichael Heron
Delivered at the UK Games Expo on Friday 1st of June, 2018 . In this seminar, Dr Michael Heron and Pauline Belford of Meeple Like Us discuss the topic of board game accessibility and why support for people with disabilities within the tabletop gaming community is important - not just for its own sake, but for all of us.
Pages referenced here:
Meeple Like Us: http://meeplelikeus.co.uk
The Game Accessibility Guidelines: http://gameaccessibilityguidelines.com/
Eighteen Months of Meeple Like Us:
http://meeplelikeus.co.uk/eighteen-months-of-meeple-like-us-an-exploration-into-the-state-of-board-game-accessibility/
Meeple Centred Design: http://meeplelikeus.co.uk/meeple-centred-design-a-heuristic-toolkit-for-evaluating-the-accessibility-of-tabletop-games/
This is an intermediate conversion course for C++, suitable for second year computing students who may have learned Java or another language in first year.
This is an intermediate conversion course for C++, suitable for second year computing students who may have learned Java or another language in first year.
This is an intermediate conversion course for C++, suitable for second year computing students who may have learned Java or another language in first year.
This is an intermediate conversion course for C++, suitable for second year computing students who may have learned Java or another language in first year.
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
A Comprehensive Look at Generative AI in Retail App Testing.pdfkalichargn70th171
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
Experience our free, in-depth three-part Tendenci Platform Corporate Membership Management workshop series! In Session 1 on May 14th, 2024, we began with an Introduction and Setup, mastering the configuration of your Corporate Membership Module settings to establish membership types, applications, and more. Then, on May 16th, 2024, in Session 2, we focused on binding individual members to a Corporate Membership and Corporate Reps, teaching you how to add individual members and assign Corporate Representatives to manage dues, renewals, and associated members. Finally, on May 28th, 2024, in Session 3, we covered questions and concerns, addressing any queries or issues you may have.
For more Tendenci AMS events, check out www.tendenci.com/events
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
2. +
Introduction
We have already touched upon the basic principles behind
Agile Programming.
Lightweight
User Centric
In this lecture we’re going to look at how it can actually be used
as a project management technique.
There are several flavours of this, with several techniques for each.
Most do not formally incorporate a project management role.
It’s considered the purview of all members.
3. +
Agile - Scrum
One flavour of agile development is known as Scrum.
It’s a framework upon which you can build your own specialised
process.
It is usually not proscriptive in terms of how things should be done.
Instead, it gives a way in which things can interrelate.
Core at the heart of Scrum is the idea that individual teams
know best about the problems they will have and the best
things to do to deal with them.
It relies on a team of motivated and multitasking members.
There’s no such thing as a team leader or project manager.
4. +
Scrum
The entirety of the team decides on how projects will be
completed.
And who is going to be responsible for completing parts of them.
A large project may involve several largely autonomous teams
each tackling a subset of the problem.
Teams are supported by two specific individuals.
A Scrum Master
The Product Owner.
The latter is the ‘client’, who is involved in making sure the
thing developed is what is actually needed.
5. +
The Scrum Master
The Scrum Master <fanfare> is the one responsible for making
sure the Scrum framework is being appropriately used.
He/she is also responsible for balancing the teams between their
internal work and product owner requirements.
The Scrum Master is responsible for facilitating the process,
allowing teams to work at their highest level of productivity.
Removing roadblocks
Facilitating meetings
Managing the ‘Product Backlog’
Organising and managing product ‘Sprints’
6. +
The Sprint
Work in Scrum progresses through a series of ‘Sprints’
A block of work, usually no longer than a month or so.
Smaller projects may have smaller sprints.
Sprints are ‘timeboxed’
They are restricted to a specific duration. You can’t delay or
rechedule them.
Sprints occur after a planning meeting.
Tasks for the upcoming sprint are identified and allocated.
At the end is a review meeting.
Where progress is evaluated against commitments.
7. +
Velocity
Scrum often incorporates a measure of team capacity known as
velocity.
This is how much work a team can do in a particular period based
on how much work has been done in other periods.
Two things are used to determine this.
The Unit of work (days, hours, ‘story points’)
Each user story in a backlog can be estimated in terms of this.
The interval
The most meaningful duration of work that can be done. Usually a
week.
Velocity is calculated by units of work completed per interval.
Initially unreliable, but with successive intervals becomes more
effective.
8. +
Velocity
Within the Scrum team, each user stories gets allocated a certain
number of units of work.
Story points are often used as an abstract scale – a fibbonaci
sequence, size of clothes, etc.
This combined with velocity gives a reasonable idea of how much
can be done during an interval.
Some teams may break it down further into velocity per individual.
Tasks are allocated within the planning meeting until the planned
units of work match velocity.
The projected velocity over a project lifetime gives a useful way of
determining what is likely to eventually be completed.
9. +
The Timebox
In some project management systems, project slippage is
anticipated.
Often represented as ‘slack’ or ‘float time’
Within Scrum, phases are timeboxed.
Each time box comes with its own deliverables, deadline (which is
immovable) and allocation of resources.
Timeboxing helps limit feature creep and scope creep.
You don’t really have the time to mess around with that kind of thing.
As such, it is largely built on task prioritisation.
MoSCoW being a common example of such a system.
10. +
The Product Backlog
During a timeboxed sprint, the Product Backlog is adjusted.
The Backlog is a prioritized feature list that is incrementally refined
during each Sprint.
To begin with, a backlog consists of everything that can be thought
of regarding required features and tasks.
This gets successively modified as the project changes, requirements
shift, and mastery over the project builds.
Typically, the backlog consists of four things:
Features to add
Bugs that exist
Technical Options
Acquired Knowledge
11. +
The Product Backlog
Some characterise the backlog as having DEEP qualities.
Detailed appropriately
Estimated
Emergent
Prioritized
Detailed Appropriately – higher priority items are described in
more detail than lower priority items.
This keeps the backlog tractable and focuses attention on the higher
priority tasks.
Estimated – Each task contains a realistic estimation of the
time required to complete them.
12. +
The Product Backlog
Emergent – As the understanding of a project changes, the backlog
will alter accordingly.
New items get added, old items get shuffled around, detail is added (or
removed) as needed.
Prioritized – The backlog is ordered with the highest priority tasks
shown first.
http://www.infoq.com/articles/pr
oduct-backlog
13. +
User Stories
The simplest and most reliable way for teams to list features is
by user stories.
These are simple descriptions of features as told from the
perspective of someone using it.
There is a standard template
As a <type of user> I want to <do something> so that <some
outcome>
As a customer, I want to browse the catalog so that I can decide
what I want to buy.
These are usually written on index cards or post-its and
arranged on walls to help facilitate the organisation of a project.
14. +
User Stories
User stories that cover large amounts of functionality are
known as epics.
‘As a user, I want to manage my account so that I have control over
how the system knows me’
Since epics are too large to be completed in a single sprint, this
gets subdivided into more manageable stories.
Sometimes dozens or hundreds depending on how epic.
‘As a user, I want to change my payment details so that my
payments come from the right account’
‘As a power user, I want to set up email notifications for alerting
me when new things are entered into the catalogue, so I don’t
need to keep checking the site’
15. +
User Stories
User stories become detailed enough to work with by two
mechanics.
Splitting them up into multiple user stories.
Adding conditions of satisfaction.
This is a high level acceptance test that will be true after a story is
complete.
‘Make sure the account can be accessed on the website’
‘Make sure the account can be accessed via a mobile phone’
These get specified early by the product owner for the project.
After negotiation with the Scrum Master and scrum teams.
16. +
Writing User Stories
User stories should ideally have the following characteristics.
Written for specific users.
While ‘As a User’ is appropriate for an example, it’s not detailed
enough for an actual user story.
As a consequence of this, this aren’t written for Product Owners.
‘As a product owner…’
An owner must be viewed in the context of their interaction of
the system.
Similarly for ‘as a developer’
Identify a value or benefit.
They need to have the ‘because’ listed.
Answer the questions: What if, Where, When, How.
17. +
The Structure of a Sprint
A sprint has a certain typical structure to it.
Planning meeting at the very start.
Deciding on the highest priority tasks, committing to which can be
done, and then developing a Sprint Backlog accordingly.
Daily sprint scrum meetings.
Very short duration, usually timeboxed.
Attended by all members, including the Scrum Master and
product owner.
A sprint review at the very end.
During this, the functionality developed during the sprint is
demonstrated.
Feedback is obtained from the product owners and other
stakeholders.
18. +
Daily Scrum Meeting
Several things get covered during the daily meeting.
Everyone updates the team on what’s been done during the last
day.
Everyone updates the team on what they’re planning to do today.
Everyone reports on anything that is causing problems.
It is the job of the Scrum Master to resolve these outside the
meeting.
For effective time management:
Meetings occur at the same time and place every day.
Meetings start on time, even if people aren’t there.
Normally only those involved in the project speak, although
everyone is welcome.
19. +
Project Burndown
As people work on tasks within Scrum, they update the Project
Burndown chart.
This shows the amount of work that remains in the current Sprint
and the overall project.
http://en.wikipedia.org/wiki/Fil
e:SampleBurndownChart.png
20. +
Why Use Scrum?
There are several well documented benefits.
Lightweight – not document free, but document light.
Improves productivity significantly in projects where the appropriate
features are in place.
User centric – the system involves users at all parts of the development
process.
High visibility of progress – project burndowns and scrum meetings all
work together to create an understanding of how the project is
proceeding.
Projects are highly adaptable – agile.
Problems are identified early.
Work done better meets the needs of the product owner as a result of
the backlog.
Can deliver at any time.
21. +
Why Not Use Scrum?
Scrum works best with experienced, motivated developers.
While you can have a few newbies ‘normalised’ by exposure to veterans, there is
a limit to how many can be dealt with.
Scrum works best with small, autonomous groups.
Five to ten people are a working, realistic maximum. If you can’t subdivide a
project into teams of this size, Scrum may not be appropriate.
Scrum works best with management and product owner buy-in.
Some organisations are averse to these kind of techniques because they don’t
‘feel’ meaty.
Scrum works best when projects can be effectively subdivided into sprints.
Multi-month monolithic phases, or extremely changeable circumstances, don’t
work well.
22. +
Who Is Using Scrum?
Lots of companies are using Scrum now.
https://docs.google.com/spreadsheet/ccc?key=0AgfBeuoRfUzNdDlMN
G82SlhmUVRhOEk0REtrdmthNWc#gid=0
Some examples:
Adobe
American Express
The BBC (for iPlayer)
Google
Linkedin
Microsoft
They are usually not the only method used.
But Scrum teams are embedded into many products, projects and
departments.
23. +
Conclusion
Scrum is an agile project management technique.
One you can profitably consider using during the module for your
assessments.
It doesn’t do away with the need for documentation, although it
does change the emphasis.
More emphasis is placed on meetings, scheduling and user
interaction than in other methodologies.
Such as the waterfall model, vanilla or iterative.
However, it is a specialised technique best used in the real
world by experienced teams.