Innovating Site Application Module

Transcription

1 Innovating Site Application Module

2 Agenda Opportunities and Outcomes Use of Agile Scrum Technical Architecture Overview Application Architecture and Workflow Review of the Site Application Module 2

3 Opportunities and Outcomes 3

4 Business Opportunity Extend the Construction Management System (CMS), create one source of data Site Application Module (SAM) is a public facing application used by Resident Engineers and Districts to manage items, estimation/projections, and payments for Construction Contracts Transportation Asset Management System (TAMS) Application Rationalization recommendations and strategy focus: l l l l Highway/IT will change SAM to use a service oriented architecture and: Adopt a strategic technology refresh and re-platforming while leveraging Agile as the software development methodology Ensure the SAM application is ADA compliant Consolidate the behind the scenes databases that provide and consume data 4

5 Technical Opportunity & Outcomes Opportunity: Further consolidation of the MassDOT application portfolio Better documentation, user guides, and less workarounds leading to data reliability Decrease support efforts needed from IT Staff Current State: Old database technology, multiple data sources, lots of manual and overnight data copy processes Complicated code base that is difficult to understand and enhance Desired Outcomes & Benefits: Migrate SAM to a reusable services based architecture and leverage Agile framework Data analyzed, consolidated, and cleaned up, and located in a new SQL 2014 environment Provided existing functionality, and added new business processes where warranted Allow field staff access via mobile devices 5

6 Use of Agile Scrum 6

7 What Is Agile Scrum? Incremental/iterative approach used by cross functional teams Provides constant feedback Prioritized backlog items based on business/customer value The goal of each iteration is to produce a working product Value focused on the left over the right Individuals and interac1ons Working so9ware over over Process and tools Comprehensive documenta1on Customer Collabora1on Responding to Change over over Contract Nego1a1on Following a Plan 7

8 Sequential vs. Overlapping Development Requirements Design Code Test Rather than doing all of one thing at a 1me Agile Scrum teams do a licle of everything all the 1me 8

9 Advantages of Agile Scrum Change is embraced End-goal can be unknown Faster, high-quality delivery l l l Reduce requirement size makes work more estimable and doable Work with small chunks of work allows for a faster development cycle and predictable delivery When complexity is reduced, certainty increases, helping troubled projects recover Strong team interaction Customers are heard l l Work on chunks of work (features) first that are prioritized by the business, lets the team know what features to work on first Focus on implementing the most valuable features first therefore delivering value to the business sooner Continuous improvement 9

10 Agile Scrum Framework at a Glance Agile Scrum projects make progress through a series of Sprints A typical duration is 2 weeks (or a calendar month at most) which leads to better metrics and predictability Product is designed, coded, and tested during a Sprint 10

11 Agile Scrum Team Roles and Responsibilities Product Owner Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI) Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results ScrumMaster Represents management to the project Responsible for enacting Agile Scrum values and practices Removes impediments Ensures that the team is fully functional and productive Enables close cooperation across all roles and functions Shields the team from external interferences Team Members Typically 5-9 people Cross-functional: Programmers, testers, designers Members should be 100% allocated to a given project Teams are self-organizing Ideally, no titles 11

12 Agile Scrum : Improved Team Communication Agile Scrum provides a sequence of periodic mee5ngs keeping teams wellaligned l l l l l Sprint Planning (every 2 or 3 weeks) Daily Agile Scrum (15 minute Standup) Sprint Review (end of each sprint) Sprint Retrospec1ve (end of each sprint) Backlog Refinement (ongoing process) Web based Agile Scrum tools such as Team Founda5on Server (TFS) l Web based tools provide distributed teams with a real-1me status view of the project and sprint. They also provide a record of all requirements, related details and history. 12

13 Common Metrics for Agile Teams Agile projects produce at-a-glance metrics; intui5ve views of team progress which help to create team cohesion: Sprint Burn-Down Release Burn-Up Features % Complete 13

14 Sprint Burn-Down Release Burn-Up The Sprint Burn-Down indicates the amount of progress against the Sprint plan that the team has completed each day: The Release Burnup indicates how much of the total project has been completed on a Sprint over Sprint basis and predicts completion timeframes: 14

15 Features % Complete 15

16 Project Roadmap Mar 17 Apr 17 Security Application Admin Monthly Projection Defects Estimates Compliance Estimate Defects Infrastructure (Performance) UAT May 17 Production Deployment Training Feb 17 Monthly Projections Jan 17 Contract Management Defects Payslips Defects Reports 16

17 Agile Scrum Ceremonies Sprint planning meeting a. Sprint Planning Session Sprint prioritization Analyze and evaluate product backlog Select sprint goal Sprint planning Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours Participants Stakeholders Scrum Master Product Owner Sprint Core Team 17

18 Sprint Planning Team selects items from the Product backlog they can commit to comple1ng Sprint backlog is created by pulling in user stories from the Product backlog Tasks are iden1fied for each user story Planning is done collabora1vely with the whole team facilitated by the ScrumMaster High to mid-level design is considered during planning. O9en, the lowest level details will be worked out during the sprint. Product Backlog Item 5822: As a Resident Engineer, I would like to be able to enter information in the Field Dates section 1. Field Dates sec1on will have the following dates: Date Sent to Contractor (gets auto populated when "Sent to Contractor" dropdown is selected as "Yes") - (MM/DD/YYYY) Contractor Signed On - (MM/DD/YYYY) Signed by RE - (MM/DD/YYYY) Signed by FRE - Hidden field. shows up only when "Es1mate Type" = Final - (MM/DD/ YYYY) 2. User shall be able to save the es1mate by clicking on the "Save" bucon. 18

19 b. Daily Scrum Daily Scrum Description: is when the team touches base to raise any impediments that are affecting the sprint. It also helps the team stay focused. What I accomplished yesterday What I plan to accomplish today Blockers/issues/risks These are not status for the ScrumMaster, but commitments in front of your peers. Participants Stakeholders Scrum Master Product Owner Sprint Core Team 19

20 The Daily Scrum Rules Ø Daily Ø 15-minutes Ø Stand-up Not for problem solving Whole world is invited Only team members, Scrum Master, product owner, can talk Daily scrum helps avoid other unnecessary meetings 20

21 c. Sprint Review Sprint Review Description: The Sprint Review takes place at the end of the sprint and is designed to gather actionable feedback on what the team completed that sprint and to provide a chance to inspect the overall plan for the product. Generally the team provides the business with demos of completed work. Participants Stakeholders Scrum Master Product Owner Sprint Core Team 21

22 d. Sprint Retrospective Sprint Retrospective Description: The Sprint Retrospective helps the team inspect and adapt its process by asking what went well during the sprint and what could have been better. In addition, the team discusses and decides on which item that could have been done better and lists it as a user story in the next sprint for improvement. Participants Stakeholders Scrum Master Product Owner Sprint Core Team 22

23 Technical Architecture Review 23

24 Where We Are Coming From 24

25 Identifying SAM Application Domains SAM v0.1 25

26 Hexagonal Architecture Contains business objects and rules for the specified domain 26

27 Integrating Multiple App Domains 27

28 Potential Future Approach: Event Driven Architecture UI Update Contract Command (Asynchronous) ESB Result Command Handling Component ESB Domain Model Persist Publish ContractUpdated Event Write Store Other consumers (Domains, external systems, etc.) Query Synchronous DTO Queries Simple Data Access Layer Read Store Update Event Handling Component 28

29 Application Architecture and Workflow 29

30 Applications and Databases in Current State Transact CPE ProjectInfo/CMS Online Bid DCD CDS SAM AEPublic FTS CIS_2000 Construc5on Public PeopleAndOrgs Transporta5on Informa5on Super Highway (TISH) DCD Lookups DCD (1) DCD (2) EBO Fiscal Database DCD (3) DCD (4) Site Applica5on Module MHDWH DCD (5) DCD (6) DCD (HQ) 30

31 Applications and Databases after SAM Upgrade Transact CPE ProjectInfo/CMS Online Bid DCD CDS SAM AEPublic FTS CIS_2000 Construc5on Public PeopleAndOrgs Transporta5on Informa5on Super Highway (TISH) DCD Lookups DCD (1) DCD (2) EBO Fiscal Database DCD (3) DCD (4) MHDWH DCD (5) DCD (6) DCD (HQ) 31

32 Applications and Databases after DCD Upgrade Transact CPE ProjectInfo/CMS Online Bid CMS CDS SAM AEPublic Construc5on Public PeopleAndOrgs Transporta5on Informa5on Super Highway (TISH) CIS_2000 EBO Fiscal Database MHDWH 32

33 Applications and Databases after CDS Upgrade Transact CPE ProjectInfo Online Bid CMS SAM AEPublic Construc5on Public PeopleAndOrgs Transporta5on Informa5on Super Highway (TISH) EBO Fiscal Database MHDWH 33

34 Construction Contract Application Flow 34

35 Services 35

36 Advantages Streamlining Construction workflow. Reusable web services( Web API 2 &.Net CoreAPI s) that can be used by multiple applications. Bootstrap makes application responsive(fluid design and mobile friendly) Bootstrap ensures consistency across the application. Development time is quicker. 36

37 Review of the Site Application Module 37

38 List of Contracts Current New 38

39 Overview Current New Segregated blocks of information 39

40 List of Items Current New 40

41 Payslips Current New 41

42 Estimates Current New 42

43 Monthly Projections Current New 43

44 New Functionality Financial Summary Bridge Informa1on 44