Hi, I'm Andrew and based in New York. I'm excited about project management and I like to work on short and long term projects.

Based on my experience I know its hard to organize topics for a project, while also putting them in a jointly used fashion to drive them to be complete.

My process to organize and drive the project goes as follows:

1. Product Backlog Creation - First off I create a list of Epics and User Stories to outline the Scope. This allows me to organize functionality and goals for the project, while showing transparency to my client.
   
   
2.  Story Point Estimation - Next I evaluate the amount of effort needed to complete tasks using T-Shirt          Sizing. This Estimation technique uses Small, Medium, Large, X-Large scale to gauge how many hours is needed based on my deductions for the task.
    
   3. Sprint Planning - Lastly to finish off the planning, I add tasks accordingly to the Sprint Backlog in order to    satisfy the Sprint Goal and Definition of Done. This allows us to start the Sprint with what is needed to complete the goal for the Sprint, as well as show what is deemed a successful status of done. "Sprint = 2-4 week development process"

For the rest of the project I incorporate refinement processes to meet expectations of the project.

My Refinement processes to keep goals aligned during development:

1. Daily Scrum - I make a daily or weekly check in meeting to talk about progress and impediments. This meeting allows me to check in with the team to find and remove bottlenecks that hinder the process of the project.
2.  Sprint Review - Once a Sprint is complete, I will go over what was completed and not completed in the      Increment with the stakeholders, as well as discuss market expectations and pivots to align goals with a market viable product.
3.  Product Backlog Refinement - "If necessary" I will redefine goals for the project according to stakeholders     feedback and incorporate new tasks to meet new goals.
4.  Sprint Retrospective - Me and the team working on the project will go over What went well, didn't go well, and should keep doing. 

Through my education at Columbia university and my certificate in project management, I've learned that using high key software to manage my projects creates a smooth transition from conception to go-live.

Project Management Software

• Jira
• Confluence
• Wrike
• Asana
• Trello

Summarization: 

I am a certified Scrum Master who can perform the duties and use the skills below to satisfy an Agile project:

Scrum Ceremonies:

• Sprint Planning
• Product Backlog Refinement
• Daily Scrum
• Sprint Review
• Sprint Retrospective

Product Backlog Creation:

• Epics
• User Stories
• Story point estimation

Scrum Artifacts

• Sprint Goals
• Definition of Done
• Sprint Backlog
• Product Backlog
• Increments
• Burn Up/Down Charts

More

• Velocity Calculation
• Kanban Boards