Connected Commerce

In Store / Web / Mobile / Social

Project Control Procedure

October 13 th – 2014

Consensus / Proprietary & Confidential

 FRAMEWORK

Initiating Planning Executing Closing

Release Sprint Daily Deploy Support

Planning Planning Meeting

Analysis

SCRUM
Team
Testing Design

Product Implementation
Owner SCRUM Product
Retrospective
Team Owner
Stakeholders
SCRUM
Team Deliverable
Product
Product
Sprint Owner
Review
Product Sprint
Backlog Backlog
Sprint
 Initiating
Costumer Product Owner

Initiating Start

Stakeholders
Costumer Interview
Request

Objective of this phase is to define i Create Business

t more clearly what the customer
Requirements

wants and get a prioritize product b
Determine
acklog that contains costumer’s viability Release
Meeting

needs so that it is executed by the

Scrum Team. Meet Scrum
Is it viable? Yes Team

Meetings: Product Release

Include Product
Backlog

Artifacts: Business Requirements,

Product Backlog
Product Backlog
Sorted

Tools: Jira, Confluence

No
Product Backlog

* Product Owner creates Jira Project and a End

Epic per each component/module
Business Requirements (Confluence)

It helps you to define, scope and track requirements for your

product or feature.

4
Product Backlog

A product backlog is a high level list of customer requirements for

the project that is owned by the product owner/manager

*Stories must to be assigned to the Scrum Master/Functional Leader by Product Owner

whom are responsible for assigning them to the scrum team and validate that all tasks them
were complete. 5
Planning Planning
Product Owner Scrum Team

Start

Objective of this phase is to have a Product Backlog

Product
Backlog,
Sprint
Planning
Analysis
Sprint Backlog, where the Scrum
Team meets with the Product Owner Define Sprint
Backlog

and determine what requirements

(of the Product Backlog) will Sprint Backlog

perform and then define and assign

tasks to perform during the sprint.
Define Tasks

Meetings: Sprint Planning

Assign
Responsible
Artifacts: Sprint Backlog, tasks
Tasks
Tools: Jira

End
* Scrum Master/Fuctional Leader creates
Stories and Tasks
Sprint Backlog

A sprint backlog contains the list of tasks that need to be completed

to implement the features planned for a particular Sprint. Ideally,
each task (Story) in a sprint is relatively short and can be picked up
by a team member rather than being assigned.

7
 Execution

Execution Scrum Team

Start

Tasks
In this phase are carried out the
tasks defined in the Sprint Backlog
and at the end a product is Execute Task

delivered to be reviewed. During

this phase daily follow-up meetings Daily

are carried out in order to know

Meeting

No
advance and locks.
Monitoring

Meetings: Daily Meeting

OK?

Artifact: Deliverable Products

Yes

Deliverable
Tools: Jira Product

End
Scrum Team Tasks

Inside sprints are conducted the following tasks by the scrum team,
below relate the tasks and responsible roles.

Architect Tester
• Analysis • Test Cases definition
• Design(HLD / LLD) • Test Cases execution
Developer Writer
• Development • Documentation
• Unit Test
 Analysis & Design

Artifacts and Tools

• HLD / LLD
o Jira – Word

• Test Cases
o TestLink
HLD / LLD

HIGH LEVEL DESIGN LOW LEVEL DESIGN

<Project Name - Customer> <Project Name - Customer>

< Internal Process Name: Quality - Development - PMO> < Internal Process Name: Quality - Development - PMO>

Revision History Revision History

Date Version Description Updated By Date Version Description Updated By

Document Approval Document Approval

Name Role Signature Name Role Signature

* Right now HLD´s / LLD´s are MS Word files, which are uploaded to
Confluence and linked them to the respective ticket.
You are expected to become Confluence templates
11
Test Cases

Testlink is a open
source tool which
allows to have a
better management
and monitoring of the
test cases. Will be
integrated with Jira
and Jenkins

12
*Test suite will soon be assessed studio for management of test cases
 Development
Development Architect/ Scrum Master/ Functional
Developers
Leader

Start
Prepare
Development
Receive Environment
Notification

Artifacts and Tools Si

Receive Codify
Notification Codify is
requered?

• Source Code

No
Execute
Configuration

No
o IntelliJ / Bitbucket (Git) Test Cases

No
Execute test cases
is required?

Configuration is
Yes

• Configuration Files
Ok?

Yes
required?

o Git (xxxx???)
Ejecuta Test
Case Yes

Prepare
Configuration

No
Environment
Ok?

• Releases Notes Ok?

No
Execute

o Jira (commits)
Configuration

No
Yes
Notify to QA Execute Unit
Test Case

End

Yes
*Prepare environment: execute at corresponding Notify
branch checkout
IDE- JIRA Integration

Inside Intellij developers

work in assigned task.
When start a new task put
it in In Progress status. In
time tracking start timer.

Through Time tracking

Through a Atlassian plugin developers can developers control
have access to the assigned tickets time task log

14
 JIRA- IDE-GIT Integration

Developers once completed

assigned tasks must Close it and
notify to the leader. Leader  checks
them were completed and change
main issue (Story/Bug/New
Feature/Improvement) to the
Resolved status.

Smart commits
allows tool
integration

15
 Release Notes

Release Notes are comments linked to Jira ticket (story), by

using the fallowing template

ID issue associated
This is provide by Jira issues link function.
Functional leader must assurance all task, bugs,
new features or improvements must be attach to
the uses cases
 
List Package / Classes
List only new classes create ( When commit since
Intellij refer Issue ID)
 
Test Classes:
List of unit test cases classes.
 
System / User preferences
List and describe system/user preferences and
values will be need modified
 
Database Script
List database script and alters needs to be
executed
 
Configuration items:
Add configuration items that need will be execute
to complete preparation process.
 
Template 16 Jira Example
 Testing
Testing Scrum Master QA Tester Produt Owner

Start Receive Prepare

Notification Acceptance
Environment
Product to test Prepare
Artifacts and Tools Testing
Environment Execute Test
Cases

Testing Result Execute Test

Cases

o Bugs(Jira) Ok?

o Findings Si

Report(Excel) Ok?

Deploy
No
Yes

Deliverable
Notify product
Product
Owner

Testing
product

Development No

End
Test Cases Manage

Testlink allows track test cases execution

18
Bug Report

QA performs reviews of the

case, if find bugs reported them
as an issue (Bug) associated
with the main issue. If
everything is ok just put a
comment as shown in the
graph and the time spent

19
Closing Closing
Scrum Team Product Owner

Start

Define Review

Sprint
At this stage the product with the Review

customer/Product Owner
(acceptance) is validated and the
Product Review Product Review

review process (lessons learned)

is carried out with the team. Retrospective

Product Backlog
Reviewed
Meetings Artifacts Quality Process Review

Sprint Review Product Backlog Control

reviewed
Learned
Retrospective Lessons learned Assurance Lessons
Meeting

End

* Parallel to closing stage, deploy and

support tasks are conducted
Retrospective

Retrospective help you track team successes and opportunities after

projects or at the end of a sprint. Use this blueprint to document what
went well, what needed improvement, and assign actions for the future

21
 Deploy
Deploy Deploy Manager

Start

Receive
Prodcut

Artifacts and Tools

Prepare

• Functional software
Production
Environment

(product) Install Produt

• Documentation: Word No

o Installation
Ok?
o User
o Configuration Yes

o Release Notes Execute
configuration
o Other files

Prepare
Documentation

End
 Continuous Integration (Jenkins)

Testing and deployment are two integral elements of web development. With some
automation mixed in, they become solutions commonly called "continuous
integration" (CI) and "continuous deployment" (CD). The "continuous" aspect of
these solutions means that your projects will be automatically tested and deployed,
allowing you to focus more on writing code and less on herding it onto servers.

23
Continuous Integration (Bamboo*)

Bamboo does more than just run builds and tests. It connects issues, commits,
test results, and deploys so the whole picture is available to your entire product
team – from project managers, to devs and testers, to sys admins.

* Currently in evaluation. Allows Jira integration

24
 Support

Support
Costumer Product Owner

Start Receive
Notification

Customer
Request
Analyze

Artifacts and Tools

Determine

• Jira ticket (Bug, New Viability

Feature, Improvement)
It is viable?

Yes

Include
Product
Backlog

No

Analysys &
Design

End