IMAT 2207 Agile Team Development Matthew Dean mjdeandmu

IMAT 2207 Agile Team Development Matthew Dean mjdean@dmu. ac. uk

Thought for the day. . .

What is the Module About? In this module you will be involved in a constrained work place simulation This means that you will be engaged in practices that you will find in an industrial setting, especially related to agile software development “Agile software development is an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end user(s). It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages rapid and flexible response to change. ”

Module Structure Team work not group work On-line resources Assignment handbook – read it! 1 x 2 hour lab per week Team schedule determines when sprint meetings take place Five minutes of feedback a fortnight New module so thing may not always go to plan!

Assessment Assessed via a series of one to one sprint meetings Any work not marked during these meetings is awarded zero! Friday blog – submitted via Blackboard First blog entry – system specification Last blog entry – module review

Agile software development. . . Concentrates on collaboration between individuals Generates working software rather than concentrating on documentation (you will still have documentation though – sample documentation provided) Working with customers and understanding their requirements Responding to changing requirements as the picture of what as required starts to emerge

Also. . . Test Driven Development (TDD) Sprints Scrum meetings C# under Visual Studio Git. Hub Azure and SQL Test design

The Need for Courage For every person and every project there is some element of fear Fear makes you tentative Fear makes you less communicative Fear makes you shy away from feedback Fear makes you shy away from mistakes We need to address the culture of fear that comes with exploring the unknown

Dealing with Uncertainty “What is going on? ” Getting inside the head of the client (so that they get the product they want) Coming to terms with the various tools you need to use (e. g. Visual Studio, Git. Hub etc. ) Working with team members Creating the documentation and understanding the notation Writing the code!

Question – How do you eat an elephant?

Answer One Bite at a Time!

The Project Process In creating a project we have four stages to think about. . . Inception Elaboration Construction Transition initial planning refining the design building the system installation support

This week Sort out team membership (3 -5 members no more no less) Make a note of your team assessment schedule (A 1, A 2, B 1, B 2) Claim your e. Grid Decide on a business scenario for your team Allocate one major table to each team member Create your team’s system specification – due in Fri of week 17 as your first blog entry Check that the selected component is suitable early on, otherwise you will have to go back to the drawing board You are individually responsible for the development of your component Significant overlap of components could result in zero marks