Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

SMS Seminar

SharePoint 2010 + Agile
by

Matthew Hodgson

on 22 September 2017

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of SMS Seminar

It's just a fad!
That's just an
excuse to do no
documentation
Another name
for
"Cowboy Coding"
team
communications
board
task
visualisation
& tracking
replace your Gannt charts!
As an author I want
to see my works in
progress so I can
remember what I
was last working on
As a system manager
I want to admin
user a/c
in order to adhere to
sys security reqs
As an author I want to
see what's going on in
the system so I can
prioritise my work
stored and tracked in
deposited and shared thru
automated reporting
captured project board decisions and approvals
SOX compliant
Situational formality
& auditing
agreed by client & Product Owner
TDD
Sign-off
Retrospectives ...
What did we do well?
What didn't we do well?
What do we need to change now to do better?
learn & adapt now rather than waiting til the end of the project!
Things we did well
Not so good
Need to change?
Get the developer colocated
Focus on the sprint
Sprint 2wks 1wks
Some tendencies to focus on understanding the 'whole' solution first, rather than just the sprint at hand
Team cohesion good
Adapted to scenario-based requirements
learning from experience
Adjusted the board at Stand-ups
task
tasks & stakeholders being engaged
planning
each sprint

deploy
team members
backlog
stakeholders to engage
Agile = reinforcing collaboration
In working together, rather than:
working in isolation
working on the whole problem
integrating solutions later
changes to
The Waterfall Way
The Agile Way
SMS Management & Technology
M +61 404 00 66 95
E mhodgson @ smsmt.com
W www.smsmt.com

Twitter @magia3e
Senior Agile Coach
Agile Samurai

enabled conversation on WIP w/ the client
enabled just-in-time changes to WIP
Lean - assisted identifing and eliminating waste

It requires a lot of discipline to work this way!
Value
Emphasis on working:
collaboratively
simultaneously
in parallel
on smaller pieces of the puzzle
Storyboards to communicate change
A3s / Epics
automation thru forms
user-
prioritised
features
story
card
acceptance
criteria
working
SharePoint
component
SharePoint implementation with Agile + UCD
It won't work here.
We're different.
We tried it
before and
it didn't work
agile?
what about using
Forrester Research on Agile:
Scrum - 10%
Agile Modelling - 6%
Feature-Driven Development (FDD) - 3.8%
Test-Driven Development (TDD) - 3.4%
eXtreme Programming - 2.9%
Lean development - 2.1%
Microsoft Solutions Framework for Agile - 1.8%
Agile Data Method - 1.6%
Adaptive Software Development - 1.3%
Crystal - 0.3%
Behaviour-Driven Development (BDD) - 0.2%
Dynamic Systems Development Method (DSDM) - 0.2%
agreed/signed-off
requirements
by Product Owner
& client
As an author I want to
see what's going on in
the system so I can
prioritise my work
As a system manager
I want to admin
user a/c
in order to adhere to
sys security reqs
persona
activity
outcome sought
As an author I want
to see my works in
progress so I can
remember what I
was last working on
requirements prioritisation
through User-Centred Design
user/business ranking of requirements priorities
requirements

SharePoint
Storyboards
Personas
Archetypal users
Captures user-requirements
Personas document in a 'light-weight' way:
Demographics - age, gender, ethnicity
Psychographics - motivations, behaviours, attitudes
Wants
Needs
Expectations
Channel preferences
Source: technet.microsoft.com/en-us/library/cc263199.aspx
transparency of work
visualise the value-chain
report velocity
identify road blocks
identify over/under estimation on the fly!
next highest priority tasks
context (storyboards)
develop solution
requirements (A3s/epics)
test/validate (prototype & TDD)
SharePoint solution design
Kanban
Benefits
Issues, risks & auditing
context diagrams
wireframes & prototypes
systems diagrams
central traceability point for all our SharePoint solution design activities
test
driven
development
conclusions
No more "analyse everything until you’re happy/comfortable"
Driven by user value - not what we thought might be good or cool
Adapting to working in 2-4 week iterations
Taking responsibility for delivering working code
Self direction: autonomy = higher motivation
Agile is hot, but it's also hard!
Faster way of working
Different way of working
More efficient, 'Lean' way of working
Reinforced visualisation of work and outputs
Increased team communication
Decreased reliance on documentation
Created a dynamic, exciting working environment

Ultimately:
Need good communication to be Agile
Change of 'success paradigm'
What the team experienced
What the client experienced
Agile - deliver value over documentation, adapt rather than blindly following a plan
Lean - reduce waste thru the project
UCD - increase buy-in from users
ISO13407 - scenario & context drives better requirements
How can I be Agile?
the hotness of agile
Matthew Hodgson
Principle Consultant
But what flavour of Agile?
things to produce
Help prioritise tasks
Lead by example
Set and obtain sign-off criteria
Members chosen as-needed based on the Project DNA
Peers guiding peers, not hierarchical management
Look!
No PM!
Product Owner
the approach
things to do
this is really just speculation!
'just enough' documentation to communicate to the client
project
DNA
project
DNA
Sprint 1
User login w/ integrated AD
Registration forms
SharePoint security architecture
Sprint 2-3
Custom forms
SharePoint EDM
SharePoint Workflow
Waterfall v. Agile
Tends towards:
Less structure
Shorter iterations
Focus on communication
Better adaptable to change
Tends towards:
More structure
Longer iterations
Focus on process
Less adaptable to change
SMS Compass Framework
Sprint 4
Public website
WCAG AA compliance
project
DNA
4 sprints x 2 weeks each
Breaking down the scope
storyboards
personas
process maps
prototype
identify business rules
SharePoint 2010
user-centred design
IA
analysis
web security
spike solution
clear the fog
SharePoint 2010 design
systems architecture solutions
workflow solutions
document management solutions
user a/c management solutions
Lots of IP already to draw from:
Tight timeframes
Still deliver the full scope of requirements
Still required to plan, analyse, design, code, test and deliver

contract negotiations took longer than expected
The problem
The Team?
Scrum Master
Hmmm, we're not delivering enough value for the first
3 months
Let's add more deliverables!
Implement a IT system that manages training documentation:

Internet/extranet/intranet
SharePoint 2010 architecture
SharePoint workflow & version control
SharePoint document management
Custom MySites - dashboards!
Custom forms
Est. 4 months to complete
the project
Lots of previous #FAIL by others in the project environment
High risk environment
High expectation of auditability of project actions & decisions
Demand for PRINCE2 project governance
The environment
My most recent SharePoint project
How could I
measure
success?
what's your
experience?
... it's something we've all experienced
Requirements
understood
documented
agreed
signed-off?
with the Waterfall way of working?
to communicate success measures to the client
to ensure success could be replicated later
Project delivered:
on time
on budget?
As low as 34% of projects are successfully delivered
43% average overrun cost
82% average overrun time
Only 52% of requirements are ever implemented
64% of functionality is rarely used
Source: Standish Group International, 2003 CHAOS Chronicles Report
Statistics on modern project delivery
Broken expectations about solution/delivery
Contingencies have to suddenly be developed
Only partial delivery of the solution – “we’ll do it in phase 2!”
Strained business relationships
Reduced trust
Reduced stakeholder confidence
No one wants to be involved with a ‘failed’ project
The result
that
What would make my next SharePoint project
successful
Delivered value
Delivered working code
Delivered rationale for requirements/specs
Documented what was created, rather than what 'might' be created
Input new ideas
Helped re/prioritise requirements
Helped us adapt and change to new requirements/needs
Every two weeks...
Client got to...
high-value incremental delivery
success
measures

My first SharePoint project?
Intranet
Extensive analysis, information architecture & design
Project time to delivery - approx 2 yrs
users helping to define the scope of THEIR work
Successful?
on-time
on-budget
Maybe not as user-friendly as I would have liked
Compass ensures our project risk footprint is minimised by leveraging SMS best-practice AS/NZS ISO 9001 management and Agile analysis activities throughout the project while delivering complete alignment with the requirements of PRINCE2 and the Project Management Body of Knowledge.
Create story cards
FIN
Track
delivered to users
How fast
we were delivering it
Analysed & designed all the options
Conversations with developers soon became about what could be delivered 'out of the box'
As the project evolved:
value to users?
but before we did any more planning ...
detailed 'speculation'
High-level project scope and plan
Outcome:
Value in integration of UCD in Agile:
Faster way of working
Different way of working
More efficient
Greater buy-in
Integrated change management
More communincation - you know whats going on, when and why
Greater transparency
More influence - you CAN add ideas when you need to!
You can adapt to change rather than trying to 'control' it
Waterfall
International Instutite of Business Analysis (IIBA) notes the following trends:

People not using traditional ways of working:
Less reliant on Use Cases
Less emphasis on requirements specification

People now looking toward new ways of working:
Increases in adoption of Agile by PMs and BAs
Moves towards user stories and scenario-based requirements
Greater emphasis on modelling, prototypes and diagrams
SMS Agile Maturity Model
custom
SharePoint 2010
MySite
4 month timeframe shortened
to 8 weeks
Breaking down project DNA
Most experiencd consultant w/ client relationship
Serve the team
Identify & remove blockers/risks
Communicate to the Project Board
Escallate decisions from team to Board as required
motivations
values your products
pain-points
Project
Collaboration
Developers in Sydney
BAs and client in Canberra
SharePoint2010 for project support
Document & picture libraries
Wikis for lightweight documentation
Blogs for retrospectives & lessons learned
Integrated Outlook calendar/tasks
Mobile & standards-based browser access
Personas!
SharePoint2010 architecture enabled iterative delivery of features prioritised by users for users
Full transcript