...

• document eclipse FTL configuration for hot FTL pages
• Proposal - One timeboxed story on FTL spike - MIFOS-4409  4409   
• Measure speed of migration of another area of Mifos. Compare established baseline (12 or so data points of historical LOC counts from git) with these new measurements.

...

"Speed of migration" will be rate of change of LOC of select source files (.jsp, *Action.java, *Controller.java, etc.) - comparing only jsp to jsp, ftl to ftl etc., over time (since we might expect, for instance, less LOC in ftl than jsp).

Measuring in this way will allow us to track a rough "burndown" of remaining UI code to convert (jsp and *Action.java LOC remaining).

Measuring testing effort

For testing related goals, we will measure:

1. time spent modifying CreateSavingsAccountTest.  For previous FTL effort, ensuring test verified all facets of page was not addressed.  New Measurement __________
2. Number of items issues caught during CSS walk through.  For previous FTL effort, number was zero since now walk through occurred.  New Measurement __________
3. Number of layout or functional bugs logged during testing phase. (missed during walk through)  For previous FTL efforts, this was typically 5-10 issues.   New Measurement:  ___________
4. Time spent by QA

...

1. manually testing the feature, including logging issues and retesting bugs fixes. For previous FTL effort, similar sized FTL conversion would be approximately 20 hours.    New Measurement _____________

More potential dev tasks

• technical improvements
  • enable instant reloading of Freemarker templates
    • (Stanley was saying he was able to hook it up to WTP and hot
      deployments?)
    • Michael Vorburger is also working on dev setup improvements, which
      includes the promise of instant FTL reloads
    • have early UI walkthrough on dev box with PM and QA
  • use JRebel
  • spend time summarizing and adding transparency to off-list work by
    Stanley Kwok & Michael Vorburger
  • could we use Spring Roo on top of Services/ServiceFacades?
  • better templates
    • reusable css pieces (use Compass?)
    • reusable ftl widgets
• measuring/managing the effort
  • as a control to measure against: estimate of how fast it's been going
    in the past e.g. Product Mix page took x days and had 23 bugs logged on
    new implementation
  • measures: what is the time required to build new FTL; how many bugs
    found by QA during manual testing; number of automated tests and time
    to write new automated tests
  • may need to measure twice - once on first try where we have trial
    and error, then second time with better defined
  • show how are new ideas are speeding up the process
• team for sprint
  • multiple devs
  • fast feedback: tight integration w/testers
    • some testing happening every day
• QA effort includes
  • new acceptance test for page (or fix/improve old test)
  • manual test pass to see if any bugs can be found in new FTL
  • seperate but associated spike on building API test for create Savings
    account
• logistical/infrastructure improvements
  • make sure all devs have fast hardware / fast internet

...