Small prototype apps were developed to evaluate the graphics
and user interface libraries. Once the libraries had been selected,
an iterative incremental approach was used. Requirements for each
iteration, a fixed period or “timebox” of two weeks, were defined
and prioritised before each iteration as MoSCoW lists based on
client feedback. MoSCoW is a “prioritisation technique used in
business analysis and software development to reach a common
understanding with stakeholders on the importance they place on
the delivery of each requirement” [14]. The client classifies the
tasks for an iteration as “Must have”, “Should have” “Could have”,
“Would like, but won’t be implemented”. The developer indicates
the expected time each task should take. To be used effectively,
timeboxing requires at most 60% of the requirements to be of type
“Must have”, so the client and developer can be confident that they
will be achieved within the timebox
Small prototype apps were developed to evaluate the graphics
and user interface libraries. Once the libraries had been selected,
an iterative incremental approach was used. Requirements for each
iteration, a fixed period or “timebox” of two weeks, were defined
and prioritised before each iteration as MoSCoW lists based on
client feedback. MoSCoW is a “prioritisation technique used in
business analysis and software development to reach a common
understanding with stakeholders on the importance they place on
the delivery of each requirement” [14]. The client classifies the
tasks for an iteration as “Must have”, “Should have” “Could have”,
“Would like, but won’t be implemented”. The developer indicates
the expected time each task should take. To be used effectively,
timeboxing requires at most 60% of the requirements to be of type
“Must have”, so the client and developer can be confident that they
will be achieved within the timebox
การแปล กรุณารอสักครู่..