Tasks

TechLead

Before quote

1. Give Technical Inputs for proposals

2. Give ballpark estimation .

Sprint initiation

1. Prepare Func Spec.Wireframe / Mockups.

2. Perform Re-Estimation and raise differences with initial estimate.
3. Preapre Architecture design .
4.Identify critical areas in technology wise, time,performance and
quality challenges.
5. Create Backlog in Jira
6. Tools and methodlogy selection.

PBR

Bi-weekly - PBR - Story point estimation

Sprint demo comments

Sprint Planning

1. Responsible for getting detailed understanding on the

requirements ,through JIRA and meetings/call.
2. Story point based expected velocity and planning for fidning
actual velocity.
3. Create QA tickets for the stories and explain to testers .
2. Capture requirement specification , to develop execution strategy
in coordination with DM and PM
3.Requirement analysis - Build to be in exact deliverable form .Data
entered and displayed are clear as per documented requirements.
Error conditions to be handled, to be exposed to user as
documented or listed
6.Decisions on the development,integration,build and testing tools
7. Plan for the effort and time for meeting customer commitments
8.Plan for the developer testing time and QA testing time.

1.Detail discussion of each story with team members and DM in

discussion room and preparing plan with dates.

Sprint execution

Sprint Release

2. Defining implementation methods : on how to split layers,

classes,public methods involved in major sequences
3. Articulate developer test procedure
4.Identify critical areas in technology wise , time and quality
challenges.
5.Making sure develeopers notes above information and understood
the details.
6.Coding - according to guidelines and best practices-if unit testing
is decided integrate unit testing framework-(if test logic is there in
jira use it) about the test scenarios while coding
7. Code review and comments incorporation.
8. Daily meeting with team members and DM
9. Ensure that team working as per stories added in JIRA

1.
2.
3.
4.

Timely completion of stories and readiness for release

Sprint release checklist execution
Release note preparation
Version tagging in SVN

Retrospect Meeting

1.Involve in meeting and discussions

2.Joint review of the build with team member

Deployment

Deployment in external server

Team Member

1. Clarification on requirements during sprint planning call

2. Estimation for the sprint and escalating if differences from initial
estimation.
3.Developers understands how end user is going to use it
3. Developer test cases are documented or listed and planned as QA tickets
in Jira
5.Design documentation is done and understood in coordination with Tech
lead
6.Coding guidleines ,best practices for using SVN ( or similar tools) and best
practices (normal and customer specific) are known.
7.Developer testing is considered in effort and planning dates ( repeated for
stressing on the aspect).

1. Daily meeting
2.Participate in discussions
2. Report progress
3. Adress clarification

1. Timely completion of tasks with quality

Delivery Manager
1.Ensure proposal and quote is delivered on time with approval of
committee.
2.Ensure the assumptions and scope are clearly stated in the
proposal.

1.Ensure approval of architecture design by experts' team.

2.Ensure reviews of architecture and comments from experts
3.Ensure review inputs are approved and incorporated.
4.Ensure team understands domains,deadlines,guidelines,tools and
practices to be followed.
5. Ensure team knows delivery timelines insync with customer
expectation.
6.Ensure backlog is created in Jira
7.Ensure visibility of the work and available in Jira
8.Ensure the probable team meets criteria for technology skills,
process and quality(identifies configuration management
strategies,tools,conventions ).
9.Ensure the estimation is reviewed.
10.Ensure expected testers know testing tools, devices needed.
1.Ensure Story point estimation is done
2.Ensure Sprint demo comments and CRs are moved to Jira and
taken for estimaiton.
1.Ensure on time delivery with QA and developer testing.
2.Ensure team is identified and team leave/availability plan is
created.
3. Ensure 100% adherence to requirements along with lead.
4.Ensure weekly meetings and Minutes of Meeting.
5.Ensures team knows end user prespective.
6.Ensure use cases or stories are validated.
7.Ensure team compare UI/UX experince with similar
offering in market and provide suggestion for improvment
8. Ensure team incorprorate styles and with competing latest or
similar products.
9. Share best practises input from the tech world
10.Ensure developer test cases are listed
11.Ensure oversee/perform smoke test to validate the
build

1. Joint review of the build

2. Attend daily meeting
3. Ensure clarifications on time
4.Analyse code review comments
5.Ensure developer testing is done and results are nalysed and
feedback is given to team.
6. Conduct smaoke test and verfiy the status before agreeing for
release.
7.Daily task tracking and ensuring status is available for all.
8.Ensure work is accoridng to a well prepared weekly plan
9.Ensure changes in initial plan are coveyed to customers.
10.Ensure changes in requirements and effort after clarifications are
conveyed to customer and total plan is reflected and approved.

1. Ensure Story adherence before approval.

2.Ensure developer testing is done and test resilts are available.
3. Ensure release checklist and release notes are available with
status for the sprint.
4. Give approval for delivery by looking at test results,coverage with
requirements, avialability of test results,meeting the customer
expectations and total quality.
5.Ensure capturing of defects
6. Action items on root causes and execution strategy to repeat
mistakes.

1.Provide inputs for solving the issues faced and for practicing the
good things happened during the sprint.

1.Verify external link working condition (conduct smoke test) and

verify mail notification to customer
2.Run checklist.
3.Capture AT defects

Program Manager
1.Arrange meeting with person bringing the lead and tech lead to
understand the project scope and technologies.
2.Follow-up delivery of the proposal and estimation.
3.Make the deliverables available in SVN.

1.Co-ordinate design discussion, requirment discussion meetings. Ensure that

architecture approval is happened
2.Coordinate with DM for resources in advance ( 2 weeks) and report to
management.
3.Identifying the point of contact for customer ,along with DM and lead making
sure the e-mail and other communication guidelines are enforced.
4 .Monitor execution strategies.
5.Flag the risks on quality, skill levels and process issues.
6.Capture effort requirement in coordination DM and PL and pass to customer.
7.Coordinate with testers for making them attending project discussiosn.

Cooridante with lead to conduct story point estimation and make sure it is
passed to customer.

1. Coordinate sprint planning meeting along with leave plans and critical
resource back-up plans.
2. Send estimate to customer and wait for approval.
3.Ensuring the points listed for TL,TM and DL are done.
4.Ensuring developers are faimilar with checklists to be used.
5.Ensuring developers are aware of the risks and contingnecy plans.
6.Capture effort for all resources.
7.Ensure the stories are updated after discussions, ensure changes in
requirements and new effort are captured.
8.Ensure proper support for demos and product support are planned along with
time and resources.

1. Ensure task plan is avaialble with delivery dates in coordination with lead.
2. Ensuring all resources knows the tasks , the deadlines and test scenarios.
3.Ensure joint review of the build with DM and lead.
4. Coordinate daily meeting
5.Ensure code review comments from team are captured and data of defects
against module, resource are captured.
6.Ensure developer test cases run and the status are captured.
7.Notifying management on the planned milestones,status of demos and
releases,data collected on Qlty.
8.Escalation of delays,leaves well in advance (2-3 days before ).Long leaves 1-2
weeks' advance.Timing changes of demos /releases ( 2 days advance )
9.Risks identificaiton, mitigation plans discussed and agreed with customer.
10.Check captured effort and test results from all resources in team.
11.Ensure the communication with all stake holders are available along with
changes,dicisions.

1. Pre release review by morning

2. Approval of release checklist and release note
3.Make sure captured effort,defects, test results, source control labelling from
all resources available for the specific sprint.
4.Plan retrospect meeting.
5.Ensure the customer demo is supported by team members.
6.Ensure defects from customer is available in Jira along with module and
responsible resource name.
7.Ensure customer comments and defects from customer are reflected in test
cases.

1.Action items listing and tracking after meeting for quality and process 2.
Improvemts for other operational issues/improvements.
2.Capture effort for all resources.
1.Planning deployment by coordinating and making sure of timely and
complete deployment.
2.Capture effort for all resources.
3.Report defects and issues to management.
4.Makes sure checklists and guidelines used are under configuration control.
5.Ensure the version is tagged for later retreival.

Remarks

Customer interface.
Joint call with Customer on archtiecture design

PBR-training-can anil help

1. Joint review of estimate with all stakeholders on a planned day.

Ideally Wednesday afternoon by Tech Lead, if sprint starts on Monday

Resource identification
Thursday to Friday or dates need to be defined
Timing of resources
QA resources in the project
Code reusability