IDs书友会 - 主题5 -  敏捷开发分享 · Agile Journey
Upcoming SlideShare
Loading in...5
×
 

IDs书友会 - 主题5 - 敏捷开发分享 · Agile Journey

on

  • 1,582 views

您是否需要在企业整体内部,跨团队成员或者太规模的工作项目当中运用精益思想与敏捷实践,加快企业流程改造?运用精益思想与敏捷开发能持续改善...

您是否需要在企业整体内部,跨团队成员或者太规模的工作项目当中运用精益思想与敏捷实践,加快企业流程改造?运用精益思想与敏捷开发能持续改善经营绩效,从而获得竞争优势。

究竟什么才是正在的敏捷了. 现在大家都在说在用敏捷的Startup, Retro, Story Board. 是不是有这些活动就是敏捷了? 怎么才能令自己的团队敏捷? 那么多敏捷的方式(XP, Scrum, Lean, Kanban etc)有什么区别了?

Statistics

Views

Total Views
1,582
Views on SlideShare
1,582
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

IDs书友会 - 主题5 -  敏捷开发分享 · Agile Journey IDs书友会 - 主题5 - 敏捷开发分享 · Agile Journey Presentation Transcript

  • Agile Intro & JourneyLawrence SongSunday, 26 May 13
  • How many ppl is usingagile methodology?Sunday, 26 May 13
  • Agenda• Are we agile?• AgileValues and Principles• Agile Processes• Case StudySunday, 26 May 13
  • Are we agile?Sunday, 26 May 13
  • Stand upSunday, 26 May 13
  • Iteration (Kick off, planning, estimate &prioritization)Sunday, 26 May 13
  • Story WallSunday, 26 May 13
  • RetroSunday, 26 May 13
  • ShowcaseSunday, 26 May 13
  • We do all the practices.Yeah, we are agile!!!Sunday, 26 May 13
  • Don’t just do agileSunday, 26 May 13
  • Be agileAgile is about culture and mindsetSunday, 26 May 13
  • Agile• Agile + Development = ContinuousDelivery• Agile + Operation = DevOps• Agile + Infrastructure = Cloud• Agile + Startup = Lean StartupSunday, 26 May 13
  • Agile Manifesto &PrincipleSunday, 26 May 13
  • Agile Manifesto• 个体和互动 高于 流程和工具 Individuals andinteraction over process and tools• 工作的软件 高于 详尽的文档 Workingsoftware over comprehensive• 客户合作 高于 合同谈判 Customercollaboration over contract negotiation• 响应变化 高于 遵循计 Responding toSunday, 26 May 13
  • 12 Principles behindthe Agile ManifestoSunday, 26 May 13
  • 我们最重要的目标,是通过持续不断地及早交付有价值的软件使客户满意。Sunday, 26 May 13
  • 欣然面对需求变化,即使在 发后期也一样。为了客户的竞争优势,敏捷过程掌控变化。Sunday, 26 May 13
  • 经常地交付可工作的软件,相隔几星期或一 个月,倾向于采取较短的周期。Sunday, 26 May 13
  • 业务人员和 发人员必须相互合作,项目中的每一天都不例外。Sunday, 26 May 13
  • 激发个体的斗志,以他们为核心搭建项目。提供所需的环境和支援,辅以信任,从而达成目Sunday, 26 May 13
  • 不论团队内外,传递信息效果最好效率也最高的方式是Sunday, 26 May 13
  • 可工作的软件是进度的首要度量标准。Sunday, 26 May 13
  • 敏捷过程倡导可持续 发。责任人、 发人员和用户要能 共同维持其步调稳Sunday, 26 May 13
  • 坚持不懈地追求技术卓越和良好设计,敏捷能力由此增强Sunday, 26 May 13
  • 以简洁为本,它是 力 少不必要工作量的艺术。Sunday, 26 May 13
  • 最好的架构、需求和设计出自自组织团队。Sunday, 26 May 13
  • 团队定期地反思如何能提高成效,并依此调整自身的举止表现。Sunday, 26 May 13
  • Agile ProcessesSunday, 26 May 13
  • ScrumMore focus on project management.Sunday, 26 May 13
  • • Daily scrum, planning and retrospective• Sprint• Burn down chartsScrumSunday, 26 May 13
  • XPFocus on development practicesSunday, 26 May 13
  • Sunday, 26 May 13
  • • Simplicity• TDD everything (Story, Bug) => almost100% test coverage• Pair programming• Continuous Integration• Collective OwnershipDevelopment PracticesSunday, 26 May 13
  • LeanEliminate WasteSunday, 26 May 13
  • Lean principles• 消除浪费 Eliminate waste• 增强学习 Amplify learning• 尽量延迟决定 Decide as late as possible• 尽快发布 Deliver as fast as possible• 增强团队能力 Empower the team• 建立完整性 Build integrity in• 看整体 See the wholeSunday, 26 May 13
  • KanbanDecrease cycle timeSunday, 26 May 13
  • Six Core Practices• Visualise• Limit WIP• Manage flow• Make policies explicit• Implement feedback loops• Improve collaboratively, evolveSunday, 26 May 13
  • • Ability to release anytime• Ability to change priority on the fly• No need in iterations• No need in estimates• Perfect flow visualization5 right reasons forKanbanSunday, 26 May 13
  • Case Study - MYOBLiveAccountsSunday, 26 May 13
  • Project 2 years ago• New team + offshore team• Legacy system• No tests at all• Manual regression• Take 4 weeks from code complete toreleaseSunday, 26 May 13
  • Introduce ProcessBacklogInAnalysisReadyfor Devin DevReadyforAnalysisReadyfor QAin QAReadyfor BATin BATReadyforDeployDeployedpickup handoverSunday, 26 May 13
  • Improve the internalquality• New simple architecture (Not the best)• 90% test coverage for new code• Code style rules• Continuous Integration (Local Build, CI)Sunday, 26 May 13
  • Reduce the cost of arelease• Automate dev/testing environment• Automate functional test for legacy• Simple manual steps to release to staging/production• Reduced release (from code complete)from 4 weeks to 2 daysSunday, 26 May 13
  • Try a few things butfailed• Kanban• TDD• Pairing• Distributed AgileSunday, 26 May 13
  • • No unit test in front-end code. Rely on functionaltests (Cannot TDD)• Devs complain some javascript code are verycomplicated• Not easy to TDD some integration code (due tooslow feedback)• Feedback cycle is too long (local development / CI)• Hacking some front-end library• Run all functional test in CI take more than 2Discover Problem 8Months agoSunday, 26 May 13
  • Architecture doesn’t allow simple designand TDDSunday, 26 May 13
  • Architecture change• Long team productivity gain• Slow down development in short term• Introduce new technologies• Build culture into the architecture• Allow TDD in front-endSunday, 26 May 13
  • Drive ArchitectureChangeSunday, 26 May 13
  • Discovered process /culture problemsSunday, 26 May 13
  • • PPL doesn’t want to change• Individual over Collaboration (Heros in theteam)• It’s too hard. There is a problem, but it’sokay. I don’t want to drive change. I wantconsensus. I don’t like you drive the change.• You owns that, I don’t want to touch it.(Silos)CultureSunday, 26 May 13
  • Burn up charts0255075100Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6Scope Dev DoneSunday, 26 May 13
  • Experiment - in a smallteamSunday, 26 May 13
  • ObjectiveNo of defects relating to the user story we are workingon once moving to ‘Ready to QA’Sunday, 26 May 13
  • • Automate all acceptance criteria• Define acceptance criteria together as a team• TDD (Ping Pong Pairing)• Raise new story for discover scope/scenarios• Determine priority together• Kanban - no estimate, no iteration,WIP, small story• Fast build + feedback• Bug repioritisation• light weight documentation• No BATHow?Sunday, 26 May 13
  • Measure of success• Number of defects raise in a story• Cycle time from in Dev to Ready for QA• Happiness. NPSSunday, 26 May 13
  • New Process - KanbaninAnalysisin Dev in QA DoneWIP: 4WIP: 4BacklogInAnalysisReadyfor Devin DevReadyforAnalysisReadyfor QAin QAReadyfor BATin BATReadyforDeployDeployedpickup handoverstorywritingSunday, 26 May 13
  • New Burn up Chart0255075100Iteration 1 Iteration 2 Iteration 3 Iteration 4Scope Dev Done0255075100Iteration 1 Iteration 3 Iteration 5Scope Dev DoneSunday, 26 May 13
  • Result• No many defects found late• Very efficient• Got Max NPS• The team own the process• Everyone is trying to improve the process• Try and see what happen. (Rather thansaying it won’t work)Sunday, 26 May 13
  • Rolling out to the restof the teamSunday, 26 May 13
  • • Most ppl don’t want to change• Most ppl based on feeling instead of facts.(being not logical)• The harder you push it the more resistanceyou will have. (it’s a journey)• You need your boss to support you• Demonstration is the keyLessons LearnSunday, 26 May 13
  • Q & ASunday, 26 May 13
  • References• http://www.targetprocess.com/blog/2009/08/5-right-reasons-to-apply-kanban.htmlSunday, 26 May 13