art of agile for shairpoint

The Art Of AgileFor

ShairPoint

hello!I am Abhinav Sabharwal

Business Analyst Agile With Capgemini, I love to give presentations.

You can find me at https://in.linkedin.com/pub/dir/Abhinav/Sabharwal

Agile Project Management

““We want to run this project as Agile”

What Do They Mean by AGILE

Most project planning meetings often begin with this opening phase .This statement then leads to a large portion of time being spent picking apart what the other party actually means

“In the majority of cases the other party is looking for flexibility and visibility during the project build phase, however they also want the project at a fixed price.


“It is possible to achieve a purely Agile project, however you need buy-in from the start on key ideals such as✘Undefined deliverables

✘Increased resources

✘Willingness to accept failure


Undefined deliverables

they will be discovered during the project, not defined prior to beginning development. This also means the duration of the project is undefined; it finishes when you're happy with the state of the product.

Increased resources

Increased resources compared to a Waterfall project – due to the undefined scope, usually at every stage a developer, tester and requirement owner is required. If you have multiple components being worked on during the iteration then this multiplies out.

Willingness to accept failure this is hard to accept, but as there is no

end goal it has to be accepted that time may be spent on a component or research that ultimately isn't required. What Agile does allow for compared with Waterfall, is to discover this earlier, perhaps within a single iteration instead of in UAT at the end of a traditional project.


“A combination of these can provide a way to add agility to the project. The project isn't Waterfall and it's not pure Agile, it's an iterative approach bringing in the best of the Agile frameworks


What Is Agile

Agile is a framework that has a few different official methodologies you can choose from. The basic tenant is to focus on making working products in an iterative fashion and adjusting to change without being stifled by rigid process.

What Is AgileAgile is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

What Is AgileIt promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change

Evolution Of AgileAs with any new technology, process or methodology in the industry there was quickly a move to label, productize and capitalize on it. This led to a narrowing and defining of multiple 'Agile Frameworks' and ultimately certification. These frameworks include:✘Scrum✘Kanban✘Lean✘Extreme Programming (XP)✘Agile Modeling

Then you define your Sprint

Start with a Product Backlog

Review Sprint after every

itration

How Agile Works

How Agile WorksI am going to outline a simple Agile/Scrum approach

✘Start with a Product Backlog. The product backlog defines, usually in the form of User Stories, what will be delivered

✘. The Product Owner, with the help of business users, create the User Stores. Using older terminology, these are the requirements.

✘The Product Owner, with the help of the business users and the key stakeholders then prioritize the items on the Product Backlog.

✘Then you define your Sprint Backlog. The Sprint Backlog defines, usually in the form of tasks, how each item on the Product Backlog will be delivered. Sprints are usually 2-4 weeks in duration. The Sprint Backlog is created by the development team. Each item on the Sprint is estimated with a number of hours. Each Sprint lasts roughly 2-4 weeks. Items

✘During the Sprint, developers meeting on a daily basis for a short meeting to discuss any roadblocks or problems they are encountering. This meeting is facilitated by the Scrum Master

whose job it is to remove roadblocks and help problem solve. The progress on the Sprint Backlog is typically tracked using the Sprint Burn down chart.✘The first underlying principle in Agile is "Customer satisfaction by rapid delivery of useful software.”. Along those lines, the ideas of "welcome changing requirements, even late in development" (the second principle) and "Working software is delivered frequently" (the third principle) both underscore the importance of adapting to change and doing it quickly

Advantage Agile✘Visibility – 'Show and Tell' sessions of a set frequency, normally budget dependant, to review progress, provide confidence that we (the supplier) are on the right track, and for us to verify that the components built haven't been misunderstood. This is highly valuable during the build phase of a project and is what we find leads to better software.

✘•Iterations / sprints – Clearly defined time blocks with set deliverables. Kanban can be mixed in to the iteration planning either with the project team or internally within the development team.

✘•Minimum Viable Product (MVP) – This is a key tenant of Lean. As quickly as possible get to a viable release. It doesn't have to be the full final product, but get something in the hands of the end

✘•Users as soon as possible. This may be seen to be too risky or contain too many unknowns, if so look to phase the project, keeping the phases small and succinct.

10 Reasons To Take SharePoint Implementation

Agile:✘1 Push past a SharePoint business as usual approach to become truly excellent at SharePoint development

✘2.Deliver SharePoint applications to the business more effectively and efficiently

✘3.Increase SharePoint end user adoption and satisfaction

✘4.Foster a leading-edge approach to business analysis and improve how you interface with the business to deliver projects

✘5.Bring a JAD/RAD approach to how your organization gathers requirements and builds software

✘6.Increase the percentage of IT projects completed on time and within budget

✘7.Improve the overall quality of SharePoint applications developed at your organization

✘8.Improve the alignment between IT, the business, and key compliance functions (such as records management and legal)

✘9.Increase the cooperation between business analysts, quality assurance, developers, and production support during the software development process

✘ 10 Do more with less

Challenges ofTaking SharePoint Implementation

Agile:✘One of the major problems with SharePoint development is that the framework is not designed with testability in mind.

✘ It is not easy to replace the SharePoint object model using Mocks/ Stubs which makes practices like unit testing more difficult in SharePoint development.

✘ Once an organization has made a decision to develop on and has collected the right people, it's time to figure out how to get the work done...the process

Agile For SharePointTaking SharePoint Implementation

Agile:Agile is rapidly gaining in popularity among software shops of all types. And for good reason. It's time it worked it's way into SharePoint development. Most companies that implement SharePoint don't realize or understand the path they are taking when they start down the path of custom SharePoint development. Most companies that implement SharePoint don't realize

after they have learned more about SharePoint – rather than what they think they want at the start. This also prevents user overload, which is always a risk when flipping the switch on a ton of new features all at once.

Agile for SharePoint can be implemented as a comprehensive process solution for software development at companies that have extensive custom development needs and large teams of developers.

Or it could be implemented by 1 developer who just wants to follow the manifesto and 12 principles when working with his SharePoint business users. The results should be the same: the consistent, rapid delivery of valuable software


Agile:Implementing SharePoint is no easy measure, regardless of your organization’s size and previous SharePoint experience.

The beauty of an agile approach to implementing SharePoint is that your users get to experience your SharePoint solutions as they evolve rather than after they’re finished. This means that stakeholders can get what they actually want at the end of the project –

Or understand the path they are taking when they start down the path of custom SharePoint development.

Assuming, however, that you are there

(you either have custom SharePoint solutions to support or have undertaken a new project to implement a custom solution),

you should select the software development methodology that has thus far, in my opinion, proven most successful.


Agile:SharePoint elements for collaboration make it easy to support communication among all interested parties to the project.

This communication can take the form of views, reports, and email alerts.

Two common type of Sprint Status Report are the Scrum Board and Sprint Burn Down Chart. The Scrum Board shows the current state and progress of all the current Sprint backlog items.

Usually the fall into four states –

✘ Not Started,✘ In Progress,✘ In Review, ✘and Completed. The Sprint Burn Down Charts graphically shows the expected drawdown of hours or points and the actual accumulation of hours or points in comparison. This kind of chart makes it easy to see where the current Sprint progress is. There are a couple of ways to manage this in SharePoint by either including a Spreadsheet or developing a list to carry the data being presented in the Chart.

Agile For SharePointConclusion

Agile is a very popular project management method. It is especially useful in managing rapid deployment of new product features in measured cycles. SharePoint 2013 can be leveraged as a platform for managing Agile

thanks!Any questions?

You can find me at [email protected]

art of agile for shairpoint

Technology