Between 2013-2015, Debbie C. and I attempted a half agile and water fall approach. This worked and didn't partially due to the roles our community leaders and studio owners had. Standard day to day operation was using 95% - 110% of our time, thus leaving little time and head space to even consider developing any kind of quality application that is thought out. We were reactive and fixing things as we were going, but didn't have a strong presence on adding more value to our standard operations. Why? Because we were busy running our dance communities.
Agile software development outlined 12 of the most important principles of development. They included communication, collaboration, open-mindedness, flexibility, and the importance of software. It is a type of incremental software development that moves along in rapid cycles--much like sprints. The results are small product releases, with each building on the previous product. Ideally teams get more work done in less time. This method proved best for time critical applications where the customer is available and willing to communicate throughout the entire life cycle of development. It requires an adaptive team willing to respond and change based on product tests and reviews.
It is concluded based on availability and commitment to the work. This project will return the classic waterfall development cycle until the need to become agile. The goals are six month minor releases with 20% new features and 80% for adjustments to current functional requirements and bug fixes.
No comments:
Post a Comment