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

Agile and ALM by example: managing the whole application lifecycle

No description
by

Clément Bouillier

on 6 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile and ALM by example: managing the whole application lifecycle

Engineering
Project Management
Support
Individuals & interactions
Process Management
User Story
Defect
Release
Automated Unit Tests
Automated UI Tests
Automated Perfs Tests
Project
Epic
Iteration Dashboard
Iteration Backlog
Task
Project Backlog
Projects Dashboard
Source code versioning
Source code metrics
Documentation
Team Member Dashboard
Iteration Burndown
Project Burndown
TFS : Work Items,
Data warehouse & Cube
Test Case
Customer Collaboration
Responding to Change
Continuous
Improvement
...and never forget that
if there is no solution,
then there is no problem
Always wonder WHY
you are doing things ?
Try, show, adjust
-> Phase locked loop
Think big, act small !
...and even if we like problems (see Shadok...), DO NOT make up some !
Choose good communication medium
Same tools for all
Trust
Know how and
when to say NO
Flow work to be
able to change
Feedback loop
The BASICS: Working Software
"Small" project from scratch
with short deadlines...
...with lot of changes
(as most of projects)...
...with a few bad outputs...
...deployed in production, starting maintenance/support in parallel...
...then over the years, more and more legacy issues arise...
...with a growing team trying to keep going on the Agile way...
...coming to shift to more and more Agile practices...
...but integrated tooling was more and more needed...
...built around User Stories & Defects...
...extending to several projects, with maintenance & support in parallel
Agile
ALM
Continuous
Integration
Business team
implication & collaboration with IT
Prefer face to face
+ whiteboard...
...and use opportunely any other medium, returning to more interactive medium when communication gets disturbed
...to organize quick produ(sort of) with Excel
...starting with Cruise Control .NET + NAnt. based on..
...with Subversion & TortoiseSVN...
Velocity
...formalized with Word documents
stored on a network share...
...like managing lot of changes with Word
and a network share could look like that...
...try to ease storage space organization with SharePoint,
so it looks like that
...need to do bug tracking, we used Mantis...
...also used to track support requests and new features...
...and then we have to manage release through Mantis and Excel...
...but without any clear vision of what is in the pipe
and without any way to prioritize between subjects...
...like regressions, trying to secure with unit tests,
but they were rather integration tests in fact...
...we do not start with unit tests and we understood then the mistake...
Agile is much more than processes ! (too often forgotten in the day and age)
...or not controlled performance issues,
trying to control with tools like OpenSTA...
...with more and more UI related issues
without any solution at this time...
...and with an increasing technical debt not measured...
Credits to Jim Highsmith & Information Architects
...then we need to scale some tools, like Iteration Backlog,
trying to include some broader concerns...
...and some diverging Team practices,
trying to limit some with tools like StyleCop & Resharper...
Design &
architecture
...in addition, start to set up a more constrained architecture
that allows better association of business and technical concerns...
...that could be called Agile and User eXperience driven...
Avoid too much proxy layers that
disrupt communication flow
Meet and communicate more and more...
...inside the team...and with Business team
...which gives a formalism that captures
requirements through business voice...
...starting with post-it and wall...
...lots of manual control and processes (error prone)
from one tool to another...
...and need for a tool allowing more
autonomy of each Team members...
...typically viewed as Product Backlog items (unit of work)...
...User Stories are splitted in Task to achieve it during an Iteration...
...which gives birth to a more conventional Iteration Backlog
...which formalize details with an A-TDD approach...
...that are used to build automated tests...
...which gives a personal overview on Iteration to each team member
taking care of the whole process across Projects...
...a synthesis view on Iteration
...to illustrate progress through the iteration...
...allowing several projects follow-up with consolidation
(including maintenance viewed as one)
...Projects are typically splitted in Epics and
then in User Stories/Defects...
...thus aggregating Task for ad-hoc budget reporting...
...which gives a structured vision of work to be done inside a particular Project
...an overview over time similar to Iteration Burndown on a single Project...
...a vision on all Projects at the same time allowing to prioritize...
...is used as "classical" Agile metric to foresee Projects delivery...
...User Stories & Defects are also used as Release content items...
...Work Items are defined through XML and can be updated easily and incrementally...
...datas from Work Items are aggregated in a warehouse...
...and then also aggregated in a cube...
...both easily queryable from Reporting Services...
...is very similar to Subversion
but integrated with Work Items...
...but surely not the "best" one nowadays...
...how do we get there ?
...to orga v²ojù...
...(sort of with Excel) to organize quick production of small functionalities...
end of 2005
2006
2007
2008
2009
April 2010
July 2010
September 2010
Requirements Management
Requirements Development
Product Integration
Technical Solution
Validation
Verification
Project Planning
Project Monitoring & Control
Configuration Management
Decision Analysis and Resolution
Measurement and Analysis
Organizational Process Definition
Organizational Process Focus
Organizational Training
Process and Product Quality Assurance
Listen to your team,
share with and encourage them to improve processes & tools
Integrated Project Management
Questions ?
...but does not exclude other tools apart from TFS,
Sonar for example to measure product quality...
Tools and processes must NOT be used to control others but by anyone for auto-control
Web based custom tool
Take in account several projects on a same application
...User Stories and Defects are organized through Theme
to compose an alive product documentation...
...tracking User Stories & Defect integration
through TFS Team Build...
...so it evolves continuously...
Visual Management based on these artefacts (and more)
Make management GO SEE, understand and be Agile
Make more user friendly TFS
Automate other processes
Full transcript