1 / 34

Property Management Product Development Update

Property Management Product Development Update. Randy Lott Director, Development AMSI. Agenda. Introductions What’s New? Customer Feedback – Challenges New Development Process Future Roadmap Q&A. Introductions. Karl Stembol – Development Manager April Bone – Quality Assurance Manager.

Samuel
Download Presentation

Property Management Product Development Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Property ManagementProduct Development Update Randy Lott Director, DevelopmentAMSI

  2. Agenda • Introductions • What’s New? • Customer Feedback – Challenges • New Development Process • Future Roadmap • Q&A

  3. Introductions • Karl Stembol – Development Manager • April Bone – Quality Assurance Manager

  4. What’s New? • Suite based installation • Common release numbering • One installation process • Suite based delivery • Common framework • eSite, eFinancials, eService and eDex all delivered together

  5. What’s New? • eSite • Letters enhancements • eService • Tighter integration with suite • eFinancials • Workflow – Check Run and Bank Reconciliation

  6. What’s New? • What’s New in eSite • Session 100 - Monday • What’s New in eService • Session 108 – Tuesday at 4:40pm (Gulf) • What’s new in eFinancials • Session 112 – Wednesday at 8:10am (Gulf)

  7. What’s New? • Release 5.5 • In beta currently • Controlled release to AMSI hosted customers in October • General Release in October/November

  8. Customer Feedback - Challenges • Major releases too few and far between • Major release scope too inflexible • What is delivered does not always reflect what is needed • No one wants to be first – quality issues • Only critical issues addressed between major releases • Delivery dates change

  9. Development Challenges

  10. Development Challenges According to the Standish Group's famous CHAOS Report of 2000, 25%*** of all projects still fail outright through eventual cancellation, with no useful software deployed. ***Sadly, this is an improvement over past CHAOS Report measurements

  11. Development Challenges A study in the United Kingdom shows that of 1,027 projects, only 13% did not fail, and waterfall-style scope management was the "single largest contributing factor for failure, being cited in 82% of the projects as the number one problem.”

  12. Development Challenges • Through Release 5.5, AMSI used the waterfall methodology • Projects were very long • Delivered what was asked for…in some cases not what was needed • Quality issues • Issues discovered late in the cycle – delivery targets were not always met • Resistant to changes in the landscape • Backlog of 4,600 system change requests

  13. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

  14. Agile – Core Values • Iterative • Continuous feedback • Continuous planning • Continuous testing • Continuous integration ……Continuous Evolution of both the project and the software

  15. Agile Development Value Proposition

  16. Agile Hallmarks • Releases and Fixed Length Iterations

  17. Agile Hallmarks • Running, Tested Software • Primary Measure of Progress • Continuous Evaluation

  18. Agile Hallmarks • Value-Driven Development • Focus on working features • Deliver business value early

  19. Agile Hallmarks • Continuous (Adaptive) Planning • Continues throughout the project • Accountable to the resources that it consumes • Deliver what is needed rather than what is asked for

  20. Agile Hallmarks • Multi-Level Planning • At the release level, we identify and prioritize the features we must have, would like to have, and can do without by the deadline. • At the iteration level, we pick and plan for the next batch of features to implement, in priority order. If features are too large to be estimated or delivered within a single iteration, we break them down further.

  21. Agile Hallmarks • Relative Estimation • Accelerate Planning • Remove unnecessary complexity

  22. Agile Hallmarks • Emergent Feature Discovery • Quick feature prioritization and estimation • Refine details as necessary

  23. Agile Hallmarks • Continuous Testing • Deterministically measure progress • Prevent Defects

  24. Agile Hallmarks • Continuous Improvement • Reflect on what is done • Has anything happened to change the landscape? • Change plans accordingly

  25. Agile Hallmarks • Small, Cross-functional Teams • More productive than larger teams • Teams have all the skills necessary to successfully deliver the planned features

  26. Agile Methodologies • Scrum • Extreme Programming (XP) • Crystal • Dynamic Systems Development Method (DSDM) • Feature-Driven Development (FDD) • Lean Software Development

  27. Why Scrum? • Flexible wrapper for existing engineering practices • Iterative and incremental • Ideal when requirements are rapidly changing • Controls the chaos of conflicting interests and needs • Improves communication and maximizes cooperation • Maximizes productivity • Teams feel good about the job that they do, their contributions, and that they are doing their best • Ideal for the AMSI culture

  28. Scrum Methodology

  29. Agile Tools Investment • Project Management software that follows the Scrum methodology • Collaborative tools for gathering requirements, tracking test results and managing source • Automated test tools

  30. Agile Customer Input • Sales, Professional Services and Support – direct input into project management system • Web access for customers to enter Requests directly into project management system • Conversion from existing tracking system – all previous requests retained

  31. Agile Maintenance • Maintenance team separated from core development team • Bi-monthly service packs (starting with Release 5.5) • Service packs are cumulative • Quicker response to high priority but non-critical issues • Zero defect objective

  32. Product Roadmap • Release 5.5 – October/November 2007 GA • Service packs every 2 months after GA • Release 6.0 – May/June 2008 GA • Service packs every 2 months after GA

  33. Product Roadmap • Release 5.5 • 5.5.1 – first bi-monthly service pack in November 2007 • Release 6.0 focus areas • Conversions • Direct conversions • Workflow • Invoice and PO Entry • DOS Gaps • Print a listing that shows all roles, groups, users and permissions associated with them • More control over check formats • Locks and Limits • Cap on concession amounts • Limit ability to backdate leasing activity

  34. Questions?

More Related