1. Johannes Brodwall Chief Scientist Smidig arkitektur

3. “How do you start a project and achieve flexibility at the beginning?”

4. “How do you {start a project} and achieve flexibility at the beginning?”

5. Keep it simple Defer commitment Inspect and adapt It depends

6. 5 tools

7. 1.Discuss the problem 2.Describe the usage 3.Pick the technologies 4.Plan the show 5.Create the software

8. When

9. MondayTuesdayWednesdayThursdayFriday Goal, Stakeholders Dev baseline Review usage Define progress, Stories Wrap up docs Dev baseline Lunch Look at what’s going on today Stakeholder, Usage Usage review, Context, Domain, Deployment Refine models Review, Retrospective Typical plan for kickoff

10. Discuss the problem

11. The problem: “A program to assign a worker to a client”

12. The problem: “A program to assign a worker to a client” (yes, it’s unclear!)

13. Form groups of 3 (or 2) You will have five minutes to discuss

14. For some user/stakeholder Who wants to achive some goal The name of the system Is a type of system Which lets them perform some operation(s). Unlike most compelling alternative This gives them some advantages.

15. For some user/stakeholder Who wants to achive some goal The name of the system Is a type of system Which lets them perform some operation(s). Unlike most compelling alternative This gives them some advantages.

16. For workers Who wants to get paid for good fun work The Awesome work system Is a digitial pimping system Which matchers worker with a client. Unlike the Excel file we’re using now This automateted, online, easy to use and.

17. Who?

18. # Clients do ??? every ??? via ??? # Dispatchers do ??? every ??? via ??? # Workers do ??? every ??? via ??? # Building Managers do ??? every ??? via ???

19. Who? Tens of Clients sign up for service a few times every year via meetings Around 20 Dispatchers assign worker teams to maintainance tasks all the time via specialized application Several hundred Workers accept tasks and confirm tasks a few times per day via mobile Hundreds of Building Managers order maintenance tasks for their buildings every few days via web

20. Who else? Payroll

21. Describe the usage

22. 1.Need: Someone identifies a need 2.Trigger: Someone does something with the system 3.The system responds in some way 4.… 5.… 6.The goal has been fulfilled

23. 1.Need: Someone identifies a need 2.Trigger: Someone does something with the system 3.The system responds in some way 4.… 5.… 6.The goal has been fulfilled

24. 1.Building manager has works that needs done (e.g. change mats) 1.Alternative: Periodic trigger 2.Building manager register works request on web site 3.Dispatcher lists unhandled work orders 1.Alternative: Dispatcher filters, searches and sorts work orders 4.Dispatcher displays work order 5.Dispatcher assign tasks to workers based on skills registered in training system 6.Worker get notified of task on their mobile 7.Worker acknowledges task 1.Alternative: If worker rejects task, system marks it as unassigned and alerts dispatcher 8.Worker performs task 9.Worker registers the task as done 10.Worker registers time and materials spent on task on mobile 11.System notifies payroll of time spent 12.System submits invoicing data to accounting system 13.Building is in great shape!

25. Worker Mobile Server Payroll Personell Accounting Dispatcher Building manager

26. Worker Mobile Server Payroll Personell Accounting Dispatcher Building manager

27. Pick the technologies

28. Constraints: Interact per user Portability Supported platform

29. Example: Dispatcher: ____ Building manager: ____ Worker: ____ Supported platform: Java stack

30. Example: Dispatcher: Web or desktop Building manager: Web or any mobile Worker: Provided mobile Supported platform: Java stack

31. Example: Dispatcher: “HTML5” Building manager: Responsive web Worker: Android Supported platform: Java stack

32. Example: Dispatcher: Responsive web SPA Building manager: Responsive web SPA Worker: Responsive web SPA Supported platform: Java stack

33. Frameworks: What can the team support Max one: Project risk or tech risk

34. Example risky project: New team New supplier New domain New codebase

35. Example risky tech: New database system New framework New programming language

36. Plan the show

37. 1.Building manager has works that needs done (e.g. change mats) 1.Alternative: Periodic trigger 2.Building manager register work order on web site 3.Dispatcher lists unhandled work orders 1.Alternative: Dispatcher filters, searches and sorts work orders 4.Dispatcher displays work order 5.Dispatcher assign tasks to workers based on skills registered in training system 6.Worker get notified of task on their mobile 7.Worker acknowledges task 1.Alternative: If worker rejects task, system marks it as unassigned and alerts dispatcher 8.Worker performs task 9.Worker registers the task as done 10.Worker registers time and materials spent on task on mobile 11.System notifies payroll of time spent 12.System submits invoicing data to accounting system 13.Building is in great shape!

38. Stories 0. (Mock work orders) 1.Complete list of work orders 2.Simple work order filter 3.Placeholder display work order 4.Placeholder assign task

39. Demo script

40. 1.Preconditions 2.Start up the system 3.What do you see? 4.Activate a function 5.What do you see? 6.Activate variations of function 7.Thus we demonstrate that we have delivered x

41. Example: Dispatch a task

42. 1.Faked: Building manager registers a work order 2.Dispatcher “logs into” web admin at http://test.workers.com/admin http://test.workers.com/admin 3.Dispatcher sees a list of missions (future: sort, filter list) 4.Dispatcher selects a mission 5.Mission will display the type of tasks associated with the mission type 6.Dispatcher clicks a task 7.Application lists all the workers that can be assigned to the task (for now, all workers are listed) 8.Dispatcher selects a worker 9.Dispatcher is returned to mission screen and the worker is listed next to the task

43. Stories – sprint 2 1.Polished list of work orders 2.Complete display work order 3.(Placeholder worker import) 4.Simple assign task

44. Create the software

45. Example: Feature: Dispatch task New codebase 5 developers

46. Solo programming

47. Integration issues Inconsistent coding Merge conflicts

48. Mob programming

49. Pair programming

50. Resource utilization vs Knowledge sharing

51. 5 tools

52. 1.Discuss the problem 2.Describe the usage 3.Pick the technologies 4.Plan the show 5.Create the software

53. 1.Describe stakeholders 2.Usage flow => context diagram 3.Use technologies you know 4.Demo script 5.Mob programming

54. Conclusion:

55. When you return: Create a elevator pitchwith your customer Create a context diagram Create a demo script for next sprint

56. Tusen takk Johannes Brodwall jbr@exilesoft.com www.exilesoft.com www.johannesbrodwall.com @jhannes