Contents

Task 1......................................................................................................................................4
Task 2......................................................................................................................................7
Solution Developer...............................................................................................................7
Business Analyst..................................................................................................................7
Solution Tester.....................................................................................................................8
Business Ambassador..........................................................................................................9
Task 3....................................................................................................................................10
Task 4....................................................................................................................................12
........................................................................................................................................13
Task 5....................................................................................................................................16
a) Project Plan................................................................................................................16
b) Project Approach Questionnaire................................................................................17
Task 6....................................................................................................................................22
What...................................................................................................................................22
So What?...........................................................................................................................22
Now What?........................................................................................................................22

Table of Figures
Figure 1: Involvement of Users............................................................................................................12
Figure 2 : Heads of Trades & Business Ambassador............................................................................13
Figure 3 : Testing................................................................................................................................14
Figure 4 : Iterative Development Cycle................................................................................................15
Task 1
Agile Development is a particular approach to handling projects that is mainly used
by software development teams. DSDM Atern is one of many leading frameworks in
Agile methodology. (Messenger, 2014)

There are eight different principles on DSDM (Dynamic System Development

Method) Atern and is able to implemented to the project to guarantee a smooth
successful outcome, which are explained by the following:

1. Focus on the business need - Every choice determined must take the
project goal into consideration to fulfil the business needs as well as delivering
it successfully. In order to successfully developed the application, Expert
Solution and the team must always have every decision having the business
need taking into account.
2. Deliver on Time - At this stage of the product , delivery of the product being
on time is vital ; this can be done via timeboxing which assist in organizing
tasks and setting a fixed time for tasks , a timeframe could also be
implemented in to ensure deadlines are being followed as well as business
priorities being a focal point at all times, thus punctuality is key at this stage .
3. Collaborate - In order to guarantee a smooth and easy process of delivering
the desktop app, the cooperation between Expert Solutions & the
Construction Agency is important as this would result in the development
process being smooth, efficient and proactive.
4. Never Compromise the quality - To ensure that there are no complications
& misunderstandings to the level of quality, the team must discuss and agree
on how to test and be consistent on the testing and review the application, this
process must be done strictly during the start of the project.
5. Build Incrementally from the firm foundations - With building the
application incrementally, the team has the advantage of having feedback and
any known knowledge on any form of errors or queries that came from the
users so that the business benefit will be delivered as early as possible.
6. Develop Iteratively - In order to successfully deliver the product and with the
business needs to be fulfilled being adaptable to change is vital; this could be
 done by allowing the combined effort of the team and the users to assist in
identifying solutions to the future changes.
7. Communicate continuously & clearly - Like with any project , poor
communication could result in the project failing, that's why the team should
have clear lines of communication , not only within the team but with the users
as well , this could be done in ways such as but not limited to : daily stand up
sessions that are both on site and remote , documentations being more
concise , utilization of workshops that involves the users and etc.
8. Demonstrate control - Everyone in the team must be proactive and show
dedication, this could be done via transparency in all plans and progress,
consistent evaluation based on the agreed quality and the user’s objectives,
all the mentioned will be implemented and organized via Timebox plans.

In regards to the differences between Agile Development versus Traditional

methods, the core difference is that of how the two tackle phases during projects,
AGILE handles phases in iterative approaches whereas the traditional approach
takes a single linear direction when handling phases.

In detail AGILE approaches the development of a software in a more concise &

user/customer friendly view , this is due to option for the users to ask for
modifications to make their experience with the application easier during the
development phase , as user stories ( suggestions for what to improve on by the
users viewpoint ) can be given during development, giving clear communication
between the team and user , this allows ease when evaluating the application and
helps in confirming whether the business need is being achieved or not through
these critiques , this further notifies the development team if there are any issues to
be known in advanced , this would allow the product to be modified at any time.

With the traditional approach (waterfall approach) it's a very linear approach in which
wastes a lot time, due to majority of the time being spent on making sure that each
stage/step is perfect , moreover the user is unable to have the opportunity make any
queries and feedbacks for the development team to utilize to ensure that business
need is met, furthermore the traditional approach can only start testing once the
whole development process is complete , thus making it merely impossible to
implement any of the users feedback, however if the developers alter anything in the
software that would require progress to be pushed back to earlier stages, meaning
more time being wasted as well as money & resources which is not applicable for
this project as this project is on a "time and materials basis" , in addition to the above
while AGILE focuses on the idea that it is a must that the project fulfils the needs of
the end users while the model waterfall follows refers to the mindset that places the
completion of the project as its focal point. (Mavuru, 2018)
 Task 2
Role: Skills Experience Weight of
contribution
Solution  Experienced in Coding (SQL, web  5+ years of experience Full Time
Develope frameworks, Front-end & backend working in an AGILE
r languages) development team
 Able to work well with other team  Bachelor’s Degree in any tech
members effectively related field such as Computer
 Excellent problem-solving skills Science or Information
 ambitious & able to motivate others Technology
 able to review and give others advice  Proven skills in developing
on code applications such as, desktop
 Excellent & Proficient communication apps, web apps & mobile apps
skills  Worked with different models
 Has Concise attention to detail in & diagrams to help other
documentation engineers
 Adequate creative mindset

Business  Able to think Analytically for problems  5+ years of experience Full Time
Analyst  Able to be organized and flexible working in an AGILE
within a group development team
 detail-oriented on documentation and  Bachelor’s Degree in any tech
records related field such as Computer
 Able to analyse data and implement it Science or Information
on the business Technology , or business
 General knowledge on functions of IT administration or related fields.
systems and tools  Proven skills in developing
 Has basic understanding on applications such as, desktop
databases, networks and related apps, web apps & mobile apps
technologies  Experience with working in a
 Able to utilize basic Microsoft development team.
Applications  Experience in testing for
 Exceptional oral skills meeting business needs.
 Capable of working in a fast paced in
development team
  Adept communication skills.

Solution  Able to think logically and rationally  5+ years of experience Full Time
Tester  Exceptional Technical  Degree on either computer
communication skills in science, or other computer-
documentations and oral related fields.
 Able to follow strict deadlines  Working and implementing
 Able to collaborate with other with various types of testing
members of the solution development  Experience in communicating
team with the team and with respect
 Must have exceptional technical skills to the evaluation from the
such as documentation, testing testing
processes, and understanding
different development cycles
(specifically DSDM atern)
Role: Skills Experience Weight of
contribution
Business  Must be proficient with computers  Must have a bachelor’s Part Time
Ambassador (computer-literate) specifically degree in any
MS applications business-related
 Perfect communication skills for courses
the development team as well as  5 years minimum of
the end user experience
 Flexible to work with  Experience in decision
 Concise with detail of records making for the purpose
 Provide a business insight to help of the successfully
aid the development team delivering the business
need
Task 3
Business Ambassador , the main representative when it comes to the business
needs of the solution development team , the weight of commitment in this role is
part time , thus there's the need to have an agreed set time to assist in making sure
that the development of the project is on the right path (specifically in terms of the
business needs) and is in communication with all the roles of the team. The
responsibilities are that of the following: (Messenger, 2014)

1. The business Ambassador must take part in all meetings and sessions
regarding the review of a phase or a product, meetings that revolve around
the design and meetings that discuss the requirements.
2. Must be the one to provides the development team with a business
perspective for solution development decisions, the purpose of this is to make
sure that the solution is fit and in line with the purpose of the business.
3. Responsible for getting in contact with end-users to involve them in the
development process, this will be a major advantage as with the business
ambassador being in contact of the end users , this would give the
development team a better chance of getting feedback that would assist in
improving the users from the user-story perspective , thus speeding up the
development process greatly.
4. Making sure that solution is developing successfully, and as already stated, to
guarantee development is on track and in line with the business needs, this
could be done via meetings or daily stand ups.
5. The business Ambassador is in charge of the business acceptance testing of
the current solution(s), checking if the product (at that current state during the
testing) is accepted by the business requirement.
6. In charge of verifying if any business participants who take part in any
deployed solutions are qualified for the role, this is done to ensure that the
solutions are properly done and executed at an adequate level.
7. Referring to scenarios that the development is facing from a business point of
view, this is done to help establish & explain the solution which will help the
development team.
 8. Responsible for producing a document that supports the overall solution for
the business user, it’s important to note that this responsibility is often shared
with the technical author and sometimes just the business ambassador.

When it comes to the importance of the business ambassador, the role is known to
be the key spokesperson of the bridge between the end-user and the solution team ,
that is why it’s crucial the business ambassador to have excellent communication
skills , the role is the one who makes sure that needs of the users is met as at the
end of the day fulfilling those needs will quickly fulfil the business need , in addition
to that being able to communicate with the user allows the development team to
easily understand and develop what the users want, furthermore the business
ambassador is the main decision maker of the solution team , meaning that it is
required by the business ambassador to be proactive and known or esteemed by the
team in making difficult decisions and communicate in order to successfully and
swiftly reach the desired business need.

From the "four hypothetical people" mentioned , the most suitable candidate would
be the business ambassador, it was the obvious choice being that the development
team needs a person who can provide the business insight to a solution, this is
crucial as this will speed up the development process and making sure that the
development teams focus is always on the business need , in addition to that , in
order to deliver a successful product the team .must involve the users during the
development stages , with the business ambassador he/she can be the one to have
all the queries , concerns & suggestions of the users and providing it to the
development team.
Task 4

Figure 1: Involvement of Users

Figure 2 : Heads of Trades & Business Ambassador
Figure 3 : Testing
Figure 4 : Iterative Development Cycle
Task 5
a) Project Plan

Task Anticipated Deliverables Status of Estimated time

task span
(days)
1st Sprint – Design of App 8
Design features to make user experience Completed 1
Discover easy and smooth
A set app-design criterion agreed by the Completed 1
Design
team
Develop Completed front-end design Completed 4
Test 2
nd
2 sprint – Database/Back-end 11
Full Details about: services, tradespeople, Completed 1
Discover
pricings & pervious work
Design of database & user & company will Completed 2
Design
interact with it
Develop A full app to be tested In progress 7
Test Pool of testers and customers feedback Not started 1
rd
3 sprint – Completing App 12
Discover List of features to incorporate & improve Not started 1
Design Plans on newly improved features Not started 3
Develop Implementing the new features Not started 7
Test Not started 1

15
 b) Project Approach Questionnaire
(Messenger, 2014)

Key Elements

Disagree

disagree
Strongly

Strongly
neutral
Agree

Agree
Acknowledging &
understanding the
approach of DSDM
and its Principles, roles ü
& responsibilities,
cycles, modelling &
philosophy
Exemplifying the
thorough & active
ü
ownership of the
project
Making the business
vision the focal point
and is making sure that
ü
every member of the
project team clearly
understands it
Making sure that
punctuality of delivery
of a solution (that is
ü
accepted after testing)
is guaranteed to make
the project successful
Requirements are able
to be ranked and that
through being flexing
with the amount of ü
what to deliver can
make the cost and time
commitments met
It is agreed by all
members that
requirements should
be explained at
distinguished level
during the earlier
ü
phases as well as
detail will be more
concise & will be more
prominent during
development stages
progressing
All members of
projects are in
agreement of the fact
that there will be
alterations to
requirements, thus ü
adapting with that
alteration will result in
success of the delivery
of the solution
It is understood by both
the Business Sponsor
& Business visionary
the importance of
being heavily involved
ü
in the business and are
able to be willing to
devote applicable
resources towards the
project.
There is a possibility
for collaboration during
the development
process between the
ü
business and the
members of the
solution development
team.
It is suitable to have
authorization of all
members of the
development team and
in addition to that,
adequate support in ü
daily decision making
is required in order to
swiftly develop the
solution via small
concise timeboxes.
The roles and
responsibilities
contained in DSDM are
correctly assigned and
the holders of those ü
roles accept and
acknowledge all the
duties required in those
roles.
Every member within
the Solution
Development team
have the required
skillset and knowledge
consisting of both soft ü
skills and technical
skills, to cooperatively
develop the business
solution that is optimal
and adequate.
Ensured that all
members in Solution
Development team that
are assign to the
project have the
ü
required experience
and skillset to support
and contribute
appropriately to the
use of timeboxing.
Ensured that all tools
to be used as well as
working practice to be
utilized are adequate ü
so that iterative
development to the
solution is successful.
During the
development stage all
types of testing and ü
reviews are fully
incorporated.
Progress of the project
is constantly measured
throughout the
ü
increments and exhibit
the delivery of
business value
There are no obstacles
and limitations that will
cause the disruption of ü
the applying DSDM to
the projects.
Task 6
(Brown, 2017)

What
The most challenging section of this task was deciding who and what members of
the FMB do to support the development team. The purpose of this issue is mainly
due to the fact that there was such a vast amount of steps and methods that could
be done by the construction agency , as well as that ; there were also some steps
that are overlapping within members and that could be done by numerous
members , such that : “x” activity could be done by admin the admin manger or could
also be executed by the admin assistant as well.

So What?
What this taught me was the importance of understanding how to facilitate certain
tasks to specific people appropriately as it will affect the rate at which the busines
need will be met, this also furthered my understanding of my role (which is to
manage a new team) , understanding the importance of the responsibilities I have to
undertake, which people are right for the role , the tasks to be given , and the
decisions needed to be taken in order to form a team that could deliver the end
solution successfully and swiftly.

Now What?
In order to prevent similar instances like this , it’s important that I better understand
the roles of a company I will be working with , such that in this case if I would repeat
this project , I would understand the roles of FMB , to be more specific , how each
one of the roles will interact with the members of the team I will be forming as
opposed to the surface level understanding of the company , furthermore I would
create more opportunities for other members so that there would not be an overlap
of roles and tasks and a wider variety of steps to take full advantage of the team.
References
Messenger, S. (2014), ‘The DSDM Agile Project Framework (2014 Onwards)’
[online]

Link - https://www.agilebusiness.org/page/Resources

Mavuru, I (2018), “Traditional VS Agile Software Development Methodologies”

[online]

Link- https://www.kpipartners.com/blog/traditional-vs-agile-software-development-
methodologies#:~:text=The%20main%20difference%20between%20traditional,in
%20Agile%2C%20it%20is%20iterative.

Dr Brown, N (2017), “Reflective model according to Rolfe et al” [online]

Link - http://www.nicole-brown.co.uk/reflective-model-according-to-rolfe/

Messenger, S. (2014), ‘The DSDM Agile Project Framework (2014 Onwards)’

[online]

Link:
https://www.agilebusiness.org/page/ProjectFramework_19_AppendixBProjectApproa
chQuestionnaire