Group Member:

Hashim Ejaz
Faizan Ahmad
Submitted To:
Sir Rizwan Ali Khan
• The discipline of planning, organizing & managing resources to
bring about the successful completion of specific project goals &
objectives.
• Term APM began to spread in 2001.
• Agile Manifesto a document prepared by professionals and
theorists in IT…
• Concept of agile is the ability to create and respond to change.
• The traditional PM approach is where all the phases of process
occur on sequence.
• Also called waterfall approach.
• Each and every project follows same lifecycle.
• Agile approach delves into evolving changes and collaborative
effort to bring out the result rather than a predefined process.
• Agile use two frame works
Scrum
KanBan
• A frame work within which people can address complex
adoptive problems productively and creatively delivering
product of the highest possible value.
• Are self organizing and cross functional
• Scrum team consist of :
• Product owner
• Scrum Master
• Development Team
• The scrum events are :
• Sprint planning
• Daily Scrum
• Sprint Review
• Sprint retrospective
• They represent work or value to provide transparency and
opportunities for inspection and adaptation.
• Scrum artifacts are :
• Increment
• Product backlog
• Sprint backlog
• Mission: Turning Visions into Business
• Wibas is a consultancy firm.
• We are your reliable partner for implementing visions,
strategies and focused improvements.
• They support clients world wide in implementing changes in their
processes and structures to successfully achieve their strategic
goals.
• we made our first steps with Scrum with our software
development projects where we were able to reach significant
improvements.
• Development, however, is only a minor part of our head office.
• But service activities are a far larger part.
• Their challenge is to improve their services.
• In this period of inspect and adapt we began with an initial
approach for a scrum for services framework
• We were aware that many iteration would be necessary until
the basic structure stabilizes
• We developed the initial approach as fellow:
• We mapped the typical practices of a service organization to the
basic scrum values.
• Allocated specific technique.
• We needed 12 sprints.
• Each sprint is of 30 days.
• The first Service Team and the responsible manager worked
together to draft the initial concept.
• The team tested the concept in practice and optimized it by
several Inspect & Adapt iterations.
• Subsequently the pioneers (out of the first team) transferred
their knowledge of the framework to another team. Thus further
practical experience flowed into the framework.
• Once the framework had been successfully implemented in two
teams, we extended the use of the framework to all other
Service Teams. At this stage, we also adapted the management
activities to follow the Scrum rules.
• Planned tasks are:
• Recurring tasks to sustain the services at their current level and
• Activities to further develop the service.
• Incidents are:
• All service inquiries from the customers.
• Product Owner: is responsible for maximizing the value of the
service and the work of the Service Team. The Product Owner is
responsible for managing the Product Backlog.
• Scrum Master: is responsible for ensuring that Scrum is
understood and enacted.
• Service Team: consists of professionals who deliver the service.
• In the Sprint Planning meeting the service team forecasts the
Product Backlog items.
• formulates the sprint goal.
• plans the tasks for the Product Backlog items.
• During the Daily Scrum meeting the Service Team synchronizes
the activities and plans for the day.
• Every Sprint closes with a Sprint Review meeting.
• The Sprint Retrospective is performed immediately after the
Sprint Review meeting.
• Scrum for Services has three artifacts:
• Product Backlog: is an ordered list of all features that might be
needed to deliver or develop the service product.
• Sprint Backlog: is the set of Product Backlog items selected for the
Sprint plus all tasks necessary for delivering the increment and
achieving the Sprint Goal plus the Incident Queue.
• Increment: is the service system provided to serve the customer
(encompasses people, technologies and processes).
• Scrum for Services is a framework for developing and
sustaining complex services that has been well proven in the
past several years in wibas.
• Scrum for Services:
• Increases effectiveness and efficiency.
• Implements strategic decisions quickly.
• Enables changes at services quickly.
• Fits to a modern work culture.