Harnessing Agile Development In Distributed Environment Dusan K Part
•Download as PPTX, PDF•
2 likes•1,517 views
Harnessing the Power of Agile Development in a Distributed Environment Part II Webminar by SD Times, Dave West (Forrester) and Dusan Kocurek. This presentation covers second part.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (11)
Similar to Harnessing Agile Development In Distributed Environment Dusan K Part
Similar to Harnessing Agile Development In Distributed Environment Dusan K Part (20)
Recently uploaded
Recently uploaded (20)
Harnessing Agile Development In Distributed Environment Dusan K Part
- 1. Dusan Kocurek Software Lab Manager, Ness Software Product Labs Part I by co-presenter Dave West not includedSenior Analyst, Forrester Research Harnessing the Power of Agile Development in a Distributed EnvironmentPart II 1
- 2. Most software development is done by distributed teams today Why distributed development? Cost savings, availability, skills 2 Challenges
- 3. 3 A Mix Of Agile And… Reality? Mix of methodologies Adaptation is key to success
- 4. Why non-Agile Customer is conservative “Waterfall is good, proven, management style” High risk project – no will and courage to implement Agile Customer’s clients want non-Agile PM Why Agile Current methods aren’t working – late releases, over-budget, team burnout Agile is a proven method Agile encourages team communication Customer is late adopter, but willing to consider if Agile can help 4 Reasons for more methodologies
- 6. Tracking
- 7. Delivery
- 9. ToolsOffshore team Customer’s team
- 11. Tracking
- 12. Delivery
- 13. Communication
- 14. ToolsMany times Agile leads to change Offshore team Customer’s team
- 16. Scrum Style
- 17. Roles
- 18. Communication
- 19. ToolsHyper-productive teams Offshore team Customer’s team 7
- 20. 8 “What are the challenges of geographically distributed development?” Team’s Communication Tools
- 21. Scrum of Scrum Integrated Scrum 9 Styles – Isolated SCRUM Coding QA Design
- 22. 10 Styles –SCRUM of SCRUM D+C+QA D+C+QA D+C+QA
- 23. 11 Styles –Integrated SCRUM Team B: D+C+Q Team A: D+C+Q Team C: D+C+Q
- 25. One Product Owner based in UK
- 26. 2 ScrumMasters in UK and Slovakia
- 28. Developers at every location
- 29. QA in UK, Slovakia 12 Scrum of Scrum style
- 31. One Product Owner per product
- 32. 3 ScrumMasters located at the same office in Romania
- 33. Teams are multi-disciplined and multi-located
- 34. Technical experts in different countries help teams to deliver www.sprintforce.com 13 Integrated Scrum style
- 35. Roles and structure Cross functional teams ScrumMasters at all locations Scrum of Scrum Product owners 14 Teams
- 36. Face to face When? Where? 15 Communication
- 37. Meet online IM, Email, Webcam Common project space When Daily At a regular time 16 Communication [Stay tuned]
- 38. Time zones Find core time Representatives 17 Time Zones
- 39. Agile and tools? Physical board is the best! I’m using Excel! Is all that enough? 18 Tools
- 40. 19 Radiators
- 41. 20 Virtual Task Boards
- 42. 21 PM Microsoft Excel Microsoft Project VersionOne ScrumDesk GreenHopper Bug trackers BugZilla Jira Mantis Mercury Quality Center Document and collaboration Microsoft SharePoint Wiki Mind map utilities Screen sharing Online meeting tools Version control systems CSV Subversion Visual Source Safe Development support Cruise Control Team Central Other tools
- 43. 22 Focus on…
- 44. Communication is a must Visibility for everyone Time zones could be advantage 23 Summary
- 45. Q+A 24 Question and Answer Session
- 46. Thank you for attending today’s webinar. Both speakers can be reached via email so that you can follow up with additional questions. Here is their contact information: Dusan KocurekSoftware Lab Manager, Ness Software Product Labs dusan.kocurek@ness.com 25 Thank you for attending!
Editor's Notes
- Scrum at locationScrum of Scrum on global level
- Teams are distributed and every team has team members in different locationsFor experienced teams understanding cultural differences
- Multi-discipline teamsLet the team to manage workDO NOT ASSIGN TASKSHead to Integrated Scrum, work should be distributed across the globeForget technologies. Forget components. You are implementing stories. Multi-discipline teams are able to develop stories, component focus is step back and will not allow you to create multi-discipline teams. Scrum master at every location help to remove obstacles which are possible to remove locally Scrum of Scrum enable to remove high level obstacles, keep all places informed about the progress and the work completed Product Owners – is it good to have more product owners? At least one at every place?
- Why - emotional level of communication, body language- Get to know each other, experience, persona, cultureWhenInception phaseProduct planningImportant events (release, demo, crunch time)Regular meetings is bestWhere- At least once in every location
- HowHave your buddy defined at other placeUse IM for critical communication use email for less critical, for proposals, operationIf call, then prefer video communicationGive every team member resources required to communicateKeep everybody on the same level of project detail’s knowledge, create common project space, share knowledge, use tweets, rss feeds, newslettersWhenBe in touch on daily baseHave short regular daily all team meetingScrum Masters have to support communication, keep it short, help to find participants
- Not a problem if time difference is low (1-2 hours)Define core time for meetings – not to stay very late, not to be very soon in an office for the meetingChallenge if time difference is 9 or more hours -> define representativesRepresentative is working in different time zone, many times customized -> Mars Pathfinder, Spirit, Opportunity project - time in sol (Mars day)
- http://www.scrumdesk.com
- Information RadiatorsVirtual boards One trackerContinuous IntegrationOne Version Control System